Methods and systems for a remote desktop session utilizing a HTTP handler and a remote desktop client common interface

ABSTRACT

Examples of methods, systems, apparatus, and machine-readable storage media are provided to facilitate access and control of a remote desktop of a remote machine by a web browser at a client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. A transcoding server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The transcoding server may receive remote desktop drawing commands from the remote machine and translate the remote desktop drawing commands into web browser drawing updates compatible with the web browser. A transcoding server may communicate with a web browser via HTTP and communicate with a remote machine via a remote desktop display protocol. A web browser may be an HTML5 browser. A transcoding server may send drawing coordinates to the web browser via an HTTP header and may use long polling.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/965,821, filed on Dec. 10, 2010.

FIELD

The subject technology relates in general to communications andprocessing, and more particularly to, methods and systems for a remotedesktop session utilizing a HTTP handler and a remote desktop clientcommon interface.

BACKGROUND

Traditional implementations of remote desktop protocols enable a remoteuser to access his or her desktop or applications from a client deviceover a LAN or WAN network topology to a server.

The traditional approach is for a software infrastructure vendor tosupport a specific public or proprietary remote desktop displayprotocol, which is native or installed on a server. To access the serverusing a remote desktop protocol, a client typically needs to have aprotocol-specific software application that executes on the user'sspecific operating system and platform or plug-in for a specificbrowser.

Conventional approaches are thus cumbersome to users. Accordingly, thereis a need for systems and methods that facilitate user interaction withan application running on a server from a client device and provide animproved experience for users at the client device.

SUMMARY

Aspects of the present disclosure may provide utilizing a transcodingserver that provides one or more web browsers' access to one or moreremote machines through a remote desktop client. Transcoding serversaccording to the present disclosure may include a module orfunctionality, e.g., machine-readable instructions, to receive requestsfrom a web browser. The transcoding servers may further include a moduleor functionality, e.g., machine-readable instructions, to translate userinput requests received (as HTTP requests) from a web browser intocorresponding input calls in a protocol/language compatible with one ormore remote desktop clients for accessing one or more remote machines.The transcoding servers can receive information/data from, e.g., drawingcommands, from one or more remote machines via the one or more remotedesktop clients and translate the information/data into aprotocol/language compatible with the associated web browser(s). Thetranscoding servers can include storage/memory functionality for holdingan image, e.g., a Java bitmap, which can be modified in response todrawing commands received from the remote desktop server. Transcodingservers may also receive from the remote desktop server and storecoordinates corresponding to the respective drawing commands.

In some applications, a transcoding server may facilitate/acceleraterendering an image of the related remote desktop(s) at the related webbrowser by creating and modifying an image of the portion of the remotedesktop that is affected by the user's input at the user device.

Aspects of the present disclosure may provide a transcoding server withlong polling functionality to handle requests from a web browser.

Aspects of the present disclosure may include or provide a web browserhaving a canvas or 2D rendering functionality.

It is understood that other configurations of the subject technologywill become readily apparent to those skilled in the art from thefollowing detailed description, wherein various configurations of thesubject technology are shown and described by way of illustration. Aswill be realized, the subject technology is capable of other anddifferent configurations and its several details are capable ofmodification in various other respects, all without departing from thescope of the subject technology. Accordingly, the drawings and detaileddescription are to be regarded as illustrative in nature and not asrestrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a display on a client device during aremote access session with a remote machine via a server.

FIG. 2A is a diagram of an example of one or more client devices eachwith a web browser connected to one or more remote machines via multiplenetworks and a server.

FIG. 2B is a diagram of an example of one or more client devices eachwith a web browser connected to one or more remote machines through anetwork and a server.

FIG. 3A is a conceptual block diagram of an example of a transcodingserver according to certain aspects of the present disclosure as used inconjunction with a web browser and a remote machine.

FIG. 3B is a conceptual block diagram of an example of a transcodingserver according to certain alternate aspects of the present disclosureas used in conjunction with a web browser and a remote machine.

FIG. 4A is a conceptual block diagram of an example of a transcodingserver.

FIG. 4B is a conceptual block diagram of an example of an alternatetranscoding server.

FIG. 4C is a conceptual block diagram of a remote desktop of a remotemachine.

FIG. 5 is a conceptual block diagram of an example of a web browser asused in conjunction with a transcoding server and a remote machine.

FIG. 6 is a conceptual block diagram of an example of a transcodingserver according to certain aspects of the present disclosure.

FIG. 7 is an example of a sequence diagram of the interactions between atranscoding server as used in conjunction with a web browser and aremote machine.

FIG. 8 is a block diagram that illustrates an exemplary computingsystem.

FIG. 9A illustrates a block diagram representing an example of a methodof accessing and controlling a remote desktop from a user device.

FIG. 9B illustrates a continuation of the FIG. 9A.

FIG. 10A is a block diagram representing an example of method offacilitating accessing and controlling a remote desktop of a remotemachine in real time by a web browser at a client device via a hypertexttransfer protocol (HTTP) utilizing a transcoding server.

FIG. 10B is a block diagram representing code of an example of amachine-readable storage medium encoded with instructions executable bya processing system to perform a method of facilitating accessing andcontrolling a remote desktop of a remote machine in real time by a webbrowser at a client device via a hypertext transfer protocol (HTTP)utilizing a transcoding server.

FIG. 10C is a block diagram module of an example of an apparatus forfacilitating accessing and controlling a remote desktop of a remotemachine in real time by a web browser at a client device via a hypertexttransfer protocol (HTTP) utilizing a transcoding server.

FIG. 11A is a block diagram representing an example of a method offacilitating accessing and controlling a remote desktop of a remotemachine in real time by a web browser at a client device via a hypertexttransfer protocol (HTTP) utilizing a transcoding server.

FIG. 11B is a block diagram representing code of an example of amachine-readable storage medium encoded with instructions executable bya processing system to perform a method of facilitating accessing andcontrolling a remote desktop of a remote machine in real time by a webbrowser at a client device via a hypertext transfer protocol (HTTP)utilizing a transcoding server.

FIG. 11C is a block diagram module of an example of an apparatus forfacilitating accessing and controlling a remote desktop of a remotemachine in real time by a web browser at a client device via a hypertexttransfer protocol (HTTP) utilizing a transcoding server.

FIG. 12A is a block diagram representing an example of a method offacilitating conducting a remote desktop session between a web browserof a client device and a remote machine via a transcoding server in realtime and utilizing hypertext markup language that supports atwo-dimensional (2D) canvas and dynamic drawing.

FIG. 12B is a block diagram representing code of an example of amachine-readable storage medium encoded with instructions executable bya processing system to perform a method of facilitating conducting aremote desktop session between a web browser of a client device and aremote machine via a transcoding server in real time and utilizinghypertext markup language that supports a two-dimensional (2D) canvasand dynamic drawing.

FIG. 12C is a block diagram of module of an example of an apparatus forfacilitating conducting a remote desktop session between a web browserof a client device and a remote machine via a transcoding server in realtime and utilizing hypertext markup language that supports atwo-dimensional (2D) canvas and dynamic drawing.

FIG. 13A is a block diagram representing an example of a method offacilitating a remote desktop session between a web browser of a clientdevice and a remote machine through a transcoding server, utilizinghypertext transfer protocol (HTTP) headers of HTTP for remote desktopsession drawing.

FIG. 13B is a block diagram representing code of an example of amachine-readable storage medium encoded with instructions executable bya processing system to perform a method of facilitating a remote desktopsession between a web browser of a client device and a remote machinethrough a transcoding server, utilizing hypertext transfer protocol(HTTP) headers of HTTP for remote desktop session drawing.

FIG. 13C is a block diagram of module of an example of an apparatus forfacilitating a remote desktop session between a web browser of a clientdevice and a remote machine through a transcoding server, utilizinghypertext transfer protocol (HTTP) headers of HTTP for remote desktopsession drawing.

FIG. 14A is a block diagram representing an example of a method offacilitating a remote desktop session between a web browser at a clientdevice and a remote desktop server at a remote machine through atranscoding server, utilizing an adapter at the transcoding server.

FIG. 14B is a block diagram representing code of an example of amachine-readable storage medium encoded with instructions executable bya processing system to perform a method of facilitating a remote desktopsession between a web browser at a client device and a remote desktopserver at a remote machine through a transcoding server, utilizing anadapter at the transcoding server.

FIG. 14C is a block diagram of module of an example of an apparatus forfacilitating a remote desktop session between a web browser at a clientdevice and a remote desktop server at a remote machine through atranscoding server, utilizing an adapter at the transcoding server.

FIG. 15A is a block diagram representing code of an example of amachine-readable storage medium encoded with instructions executable bya processing system to perform a method of facilitating accessing andcontrolling a remote desktop of a remote machine in real time from a webbrowser at a client device via a hypertext transfer protocol (HTTP)handler and a remote desktop client adapter for a transcoding server.

FIGS. 15B-15C are block diagrams representing an example of a method offacilitating accessing and controlling a remote desktop of a remotemachine in real time from a web browser at a client device via ahypertext transfer protocol (HTTP) handler and a remote desktop clientadapter for a transcoding server; FIG. 15C is a continuation of FIG.15B.

FIGS. 15D-15E are block diagrams of modules of an example of anapparatus for facilitating accessing and controlling a remote desktop ofa remote machine in real time from a web browser at a client device viaa hypertext transfer protocol (HTTP) handler and a remote desktop clientadapter for a transcoding server; FIG. 15E is a continuation of FIG.15D.

While certain embodiments are depicted in the drawings, one skilled inthe art will appreciate that the embodiments depicted are illustrativeand that variations of those shown, as well as other embodimentsdescribed herein, may be envisioned and practiced within the scope ofthe present disclosure.

DETAILED DESCRIPTION

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology may bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a thorough understandingof the subject technology. However, it will be apparent to those skilledin the art that the subject technology may be practiced without thesespecific details. In some instances, well-known structures andcomponents are shown in block diagram form in order to avoid obscuringthe concepts of the subject technology. Like components are labeled withidentical element numbers for ease of understanding.

Prior approaches using hypertext markup language (HTML) have requiredthe use of browser specific plug-ins as a method to create a better userexperience by accelerating video and audio for example. Browser plug-insdo not achieve HTML browser independence across the competinginfrastructure vendors.

Infrastructure vendors are competing heavily in the “proprietary” remotedesktop protocols and are focused on modest improvements over time toimprove the user experience. The user experience while using a remotedesktop protocol is a primary differentiator between the infrastructurevendors. There are, however, no known efforts to enable the user andcustomer to have a single unified method to have remote access to theirhome, work or mobile Windows, Mac or Linux environments.

In some aspects, embodiments of the subject technology can eliminate orreduce the need for the installation of “proprietary” protocols on auser's device (or a client device) for accessing a remote machine duringa remote desktop session. A remote machine, or remotely accessedmachine, may include a remote desktop server. By enabling the user touse a single method to access their remote desktops with an “openstandard” technology like HTML5, the requirements placed on a user'sdevice, e.g., a smart phone, can be greatly reduced.

In some aspects, embodiments of the subject technology can reduce oreliminate the need for installation of client software and/or a browserplug-in on the user's client device.

In some aspects, embodiments of the subject technology can achieve arobust user experience that one would expect from a local executingapplication on a personal computing desktop.

In some aspects, embodiments of the subject technology canadvantageously utilize 2D rendering capability of suitable web browsersand replace proprietary rendering protocols with the 2D drawingcapabilities of a browser running on the user's client device.

In some aspects, embodiments of the subject technology can allow a userto easily access one or multiple open remote desktops across multipleservers and maintain their exact state from information stored inreal-time on an associated web server having protocol translationfunctionality that can function as a common interface between push-typeprotocol employed by most remote desktop protocols and the pull-typeprotocol employed by HTTP, also referred to herein as a “transcodingserver,” which the user may access via a web browser having 2D renderingcapability. Doing so can allow the user to render a remote display of acurrently open session in a few seconds. Thus, as the user switches fromclient device to client device, the exact state of a particular remotedesktop is preserved and is re-rendered based on the capabilities ofeach display device. Effectively the user's multiple desktops can beconfigured to be always on and ready to be displayed on demand. Theuser's remote desktops can be configured to be accessed at any time andfrom any location.

Prior to the subject technology as described herein, because HTTP (apull-type protocol) and most remote desktop display protocols (push-typeprotocols) are incompatible, it has generally been recognized by thoseskilled in the art that proprietary software and/or downloadableplug-ins were necessary for a web browser in order to have a remotedesktop session using an HTTP on one end and a remote desktop displayprotocol on the other end.

In some aspects, embodiments of the subject technology can enable a userof any endpoint device with a web browser having 2D renderingcapabilities, e.g., an HTML5 browser, to display one or more remotedesktop sessions in a single or multiple browser windows. Embodiments ofthe present disclosure can accordingly eliminate the need forinstallation on a client device of proprietary or open source clientapplications for remote desktop access. Embodiments of the presentdisclosure can establish and maintain simultaneous remote desktopconnections to a single or multiple Windows, Mac OS, or Linux serversand enable all remote sessions to be displayed and interactedindependently within the user's browser application. Embodiments of thepresent disclosure can be rendered in real-time and be displayed as aweb page on the remote client, e.g., a user device such as a smartphone. All user mouse, touch and keyboard input may be captured withinthe browser window and converted into the input format needed by theremote desktop machine, which may utilize common desktop protocols,e.g., independent computing architecture (ICA) by Citrix Systems, remotedesktop protocol (RDP) by Microsoft, and PC-over-IP (PCoIP) by Taradici,etc. Embodiments of the present disclosure can maintain open connectionsto the host servers at all times allowing single or multiple endpointdevices to be interactively connected and disconnected to the remotesessions instantly. Remote sessions never need to be disconnected fromthe servers as embodiments of the present disclosure can maintain activeconnections to the desktop. Active sessions can be resized and adjustedfor best display and user experience to utilize the full capability ofthe user's access device.

In some aspects, embodiments of the subject technology can reduce oreliminate the requirement for a local client application, e.g., a webbrowser, to support a vendor specific remote desktop protocol.Embodiments of the present disclosure can allow a browser with 2Drendering capability to run on any hardware, any operating system andany form-factor for the user to access her or his remote desktop orapplications. A user can simply point the browser, e.g., an HTML5compatible browser such as Google Chrome, to a respective predetermineduniform resource locator (URL) for one or more remote machinesconfigured as a remote desktop application servers. The browser canaccess a transcoding server that can translate or transcode between theprotocol used for the browser and the protocol used for the remotemachine(s). The transcoding server can be public/private cloud-based,and the access to the transcoding server can utilize HTTPS protocol. Thetranscoding server can authenticate the connection between the remotemachine and a remote desktop client, render the desktop of the remotemachine(s) in real-time, and transmit that rendering to the browser viaHTTP so that the browser can display the rendering in HTML5 canvas.Accordingly, embodiments of the present disclosure can function as, orprovide, a virtual desktop and application server that connects to oneor multiple remote desktop servers, e.g., Citrix XenDesktop with ICA,Microsoft Windows Client and Server with RDP, and VMware View withPCoIP, etc.

Prior to HTML5 supporting canvas 2D real-time drawing primitives, HTMLalone was not seen as a practical rendering technology due to the staticnature of the rendered objects. As used according to the presentdisclosure, HTML5, and similar browser languages, can enable a new userrobust experience due to the ability of rendering in 2D, 3D andmultimedia video/audio objects on the client platform; HTML5 can also,in some cases, utilize hardware acceleration for such rendering. Aspectsof the subject technology can facilitate enhanced user experience forremote desktop sessions by providing platform-independent techniquesthat allow real time access to remote machines and do not require theclient device to have proprietary software or plug-ins. Moreover, theremote machines are not required to have HTTP or HTML compatibility forthe remote desktop sessions.

As described herein, aspects of the subject technology can reduce orminimize traffic between a browser and a transcoding server accordingthe present disclosure. The reduction in traffic can be facilitated byvarious aspects of the subject technology including, but not limited to,implementation of long polling for drawing requests received from a webbrowser, providing to a web browser only image portions from a remotedesktop that have changed and need to be updated (rather than the imageof the entire remote desktop), and placing coordinates for updated imageportion(s) into a header of a single HTTP transmission response. Thereduction of traffic to and from a browser can facilitate a remotedesktop session that provides a real time user experience, e.g., a userexperience with few if any perceivable delays in the round trip time(delay) for user inputs to travel from a client device, to the remotemachine, and a corresponding update of the remote desktop showing up onthe client device. In exemplary embodiments, such delay may be below,e.g., 100 milliseconds, so that most users will not perceive any delayat all.

FIG. 1 shows an example of a display at a client device with a largescreen during a remote desktop session with a remote machine via aserver. The display 100 includes the local desktop 110 of the clientdevice, a web browser window 120 that in turn includes a remote viewwindow 130 showing an image 132 of a remote desktop of the remotemachine, which image includes, in this example, folder and shortcuticons in addition to a remote web browser application 140 running on theremote machine. The remote view window 130 may have a height H and awidth W, and remote view window 130 may be resized (e.g., to be madelarger to cover the entire local desktop 110 or be made smaller). Theimage 132 of the remote desktop 130 and remote application 140 are basedon display output data of the remote desktop 130 and remote application140 from the remote machine transmitted to the client device via theserver.

As was noted previously, aspects of the present disclosure can includeor utilize a HTML5 compatible web browser having a 2D canvas, e.g., 530in FIG. 5. The HTML5 specification provides for a 2D canvas, whichallows for dynamic, real-time, scriptable rendering of 2D shapes andbitmap images. In one aspect, being scriptable can mean or includereference to utilizing JavaScript for rendering a 2D image. The canvasconsists of a drawable region defined in HTML code with height and widthattributes. JavaScript code may access the area through a full set ofdrawing functions similar to other common 2D APIs, thus allowing fordynamically generated graphics.

As shown in FIGS. 2A-2B, an overall architecture of exemplaryembodiments of the present disclosure may contain three parts: a clientdevice (or a user's device) containing a browser, e.g., an HTML5compatible browser; a server, e.g., a Java web sever, that is configuredto function as a transcoding server, translating between differentprotocols; and a remote machine to which the client device isconnecting. As shown and described for FIGS. 3A-3B, a transcoding servermay include three main sections: a remote desktop client wrapper oradapter, a drawing commands queue, and a web application container. Theweb application container can include various elements or components,e.g., a hypertext transfer protocol (HTTP) handler, a long pollinghandler, and a drawing requests queue, as shown and described withreference to FIGS. 2A-11. In an alternate embodiment, a drawing commandsqueue may be a part of a web application container.

FIG. 2A is a diagram of an example of client devices such as thosehaving a web browser connected to multiple remote machines throughmultiple networks and a server. The system 200 may include one or moreremote client devices 202 in communication with one or more remotemachines 204 via a server computing device 208 (server) via one or morenetworks 206. In one aspect, the server 208 is configured to allowremote sessions (e.g., remote desktop sessions) wherein users at clientdevices 202 can access applications and files on one or more remotemachines 204 by logging onto the server 208 from a client device 202over one or more networks 206.

FIG. 2B is a diagram of an alternate example of one or more clientdevices connected to one or more remote machines through a network and aserver. As shown in the drawing, the server 208 associated with theremote machines 204 can be connected to network 206, for example, in ahub and spoke configuration.

By way of illustration and not limitation, in one aspect of thedisclosure, stated from a perspective of a remote machine side (treatinga remote machine 204 as a local device and treating a client device 202as a remote device), an application is executed (or runs) at a localdevice 204. While a client device 202 may receive and display a view ofthe application on a display local to the client device 202, the clientdevice 202 does not execute (or run) the application at the clientdevice 202. Stated in another way from a perspective of the client side(treating a remote machine 204 as a remote device and treating a clientdevice 202 as a local device), a remote application is executed (orruns) at a remote machine 204, and while a client device 202 may receiveand display a view of the remote application, the client device 202 doesnot execute (or run) the remote application locally at the clientdevice.

By way of illustration and not limitation, a client device 202 canrepresent a computer, a mobile phone, a laptop computer, a thin clientdevice, a personal digital assistant (PDA), a portable computing device,or a suitable device with a processor. In one example, a client device202 may be a smartphone (e.g., iPhone, Android phone, Blackberry, etc.).In certain configurations, a client device 202 can represent an audioplayer, a game console, a camera, a camcorder, an audio device, a videodevice, a multimedia device, or a device capable of supporting aconnection to a remote server. In a preferred example, a client device202 is mobile. In another example, a client device 202 can bestationary. According to one aspect of the disclosure, a client device202 may be a device having at least a processor and memory, where thetotal amount of memory of the client device 202 could be less than thetotal amount of memory in a remote machine 204 or a server 208. In oneexample, a client device 202 does not have a hard disk. In one aspect, aclient device 202 has a display smaller than a display supported by aremote machine 204 or a server 208. In one aspect, a client device mayinclude one or more client devices.

In one preferred aspect, a server 208 or a remote machine 204 mayrepresent a computer. In another aspect, a server 208 or a remotemachine 204 may represent a laptop computer, a computing device, avirtual machine (e.g., VMware® Virtual Machine), a desktop session(e.g., Microsoft Terminal Server), a published application (e.g.,Microsoft Terminal Server) or a suitable device with a processor. In onepreferred example, a server 208 or a remote machine 204 is stationary.In another aspect, a server 208 or a remote machine 204 can be mobile.In certain configurations, a server 208 or a remote machine 204 may beany device that can represent a client device. In one aspect, a server208 may include one or more servers.

In one example, a first device is remote to a second device when thefirst device is not directly connected to the second device. In oneexample, a first remote device may be connected to a second device overa communication network such as a Local Area Network (LAN), a Wide AreaNetwork (WAN), and/or other network.

When a client device 202, a server 208 and a remote machine 204 areremote with respect to one another, a client device 202 may connect to aserver 208 over a network 206, and a remote machine may connect to aserver 208 over a network 206 via a network connection, for example, amodem connection, a LAN connection including the Ethernet or a broadbandWAN connection including DSL, Cable, T1, T3, Fiber Optics, Wi-Fi, or amobile network connection including GSM, GPRS, 3G, WiMax or othernetwork connection. A network 206 can be a LAN network, a WAN network, awireless network, the Internet, an intranet or other network. A network206 may include one or more routers for routing data between clientdevices and/or servers. A remote device (e.g., client device, server) ona network may be addressed by a corresponding network address, such as,but not limited to, an Internet protocol (IP) address, an Internet name,a Windows Internet name service (WINS) name, a domain name or othersystem name. These illustrate some examples as to how one device may beremote to another device. But the subject technology is not limited tothese examples.

According to certain aspects of the present disclosure, the terms“server” and “remote server” are generally used synonymously in relationto a client device, and the word “remote” may indicate that a server isin communication with other device(s), for example, over a networkconnection(s).

According to certain aspects of the present disclosure, the terms“client device” and “remote client device” are generally usedsynonymously in relation to a server and/or a remote machine, and theword “remote” may indicate that a client device is in communication witha server(s) and/or a remote machine(s), for example, over a networkconnection(s).

In one aspect of the disclosure, a “client device” may be sometimesreferred to as a client, a user device, a user's device or vice versa.Similarly, a “server” may be sometimes referred to as a server device orvice versa. A server is sometimes referred to as a web server. Exemplaryembodiments of the present disclosure include use of web servers withtranscoding functionality, e.g., transcoding servers.

In one aspect, the terms “local” and “remote” are relative terms, and aclient device may be referred to as a local client device or a remoteclient device, depending on whether a client device is described from aclient side or from a server side or a remote machine's side,respectively. A remote machine may be referred to as a local machine ora remote machine, depending on whether a remote machine is describedfrom the remote machine's side or from a client or server side.Similarly, a server may be referred to as a local server or a remoteserver, depending on whether a server is described from a server side orfrom a client side or a remote machine's side, respectively.Furthermore, an application running on a remote machine may be referredto as a local application, if described from a remote machine's side,and may be referred to as a remote application, if described from aclient side or a server side.

In one aspect, devices placed on a client side (e.g., devices connecteddirectly to a client device(s) or to one another using wires or a shortrange wireless connection (e.g., Bluetooth)) may be referred to as localdevices with respect to a client device and remote devices with respectto a server. Similarly, devices placed on a server side (e.g., devicesconnected directly to a server(s) or to one another using wires or ashort range wireless connection (e.g., Bluetooth)) may be referred to aslocal devices with respect to a server and remote devices with respectto a client device.

FIG. 3A is an example of a conceptual block diagram of a system 300Aincluding a transcoding server 330 according to certain aspects of thepresent disclosure as used in conjunction with a web browser 312 and aremote machine 320. A client device 310, such as a smart phone or laptopcomputer, is depicted along with a web browser having (i) a canvas 316,e.g., the web browser 312 supports a 2D rendering canvas, and (ii) ascript client 314, e.g., a JavaScript client in a preferred embodiment.

Transcoding server 330 can include three main functional blocks ormodules: a web application container 340, a remote desktop clientadapter 350, and a drawing commands queue 360 that includes a sharedmemory. The web application container can include an HTTP handler 344for handling HTTP requests from the web browser and HTTP responses tothe web browser. In some embodiments, the web application container 340may also include a long polling handler module 342, as shown. The remotedesktop client adapter 350 can be configured to interface with a remotedesktop client 352, e.g., from a third-party vendor, for communicationwith remote machine 320, which may include a remote desktop server 322,as shown. Embodiments of a transcoding server 330 can be configured toprovide an application framework for hosting one or more webapplications and/or function as a Java web application container thatcan run Servlets. In some aspects, a remote desktop client adapter 350may be referred to as a remote desktop client common interface.

The remote desktop client 352 may function to communicate with theremote desktop server 322 of the remote machine 320 using a remotedesktop display protocol. The remote desktop client sends a user's inputto the remote machine, and receives drawing data from the remote machinevia its specific remote desktop display protocol.

In one aspect, a remote desktop server 322 may refer to a softwareinstalled on a remote machine 320, and a remote desktop server 322 mayallow applications, particularly those including graphical applications,which run on the remote machine 320, to be displayed at a machine thatis separate and distinct from the remote machine 320 (e.g., clientdevices 310). Remote desktop server 322 may allow drawing commandsrepresenting an image of a desktop of the remote machine to betransmitted to the separate machine (e.g., transcoding server 330). Inone aspect, remote desktop client 352 may refer to a software installedon the machine that is separate and distinct from the remote machine 320(e.g., transcoding server 330). Remote desktop client 352 may sendrequests to remote desktop server 322 via a remote desktop displayprotocol and in response receive the drawing commands representing theimage of the desktop of the remote machine via the remote desktopdisplay protocol.

In operation, the web application container 340 can function to receiveand respond to the JavaScript client's HTTP requests. In oneimplementation, a Servlet container can be used but the same result canbe achieved using any similar web application framework, such asRestlet, for example. The remote desktop client adapter 350 may providea common interface between any remote desktop client and the drawingcommands queue/the web application container.

The remote desktop client adapter 350 may receive a user's inputinformation, data, or commands (e.g., mouse, keyboard, and touch events)from HTTP handler 344 and translate the input information/commands intorespective remote desktop input calls, which are sometimes referred toas remote desktop input commands. The remote desktop client adapter 350may also translate the drawing commands of the remote desktop, e.g., GDIdrawing commands, received from remote desktop server 322 (via a remotedesktop display protocol and remote desktop client 352) into Javagraphics application programming interface (API) commands. Java graphicsAPI commands in themselves are not suitable for the web browser; butthey are an intermediary step towards achieving browser compatibility.The remote desktop client adapter may then execute those Java graphicsAPI commands, i.e., drawing into an off-screen Java bitmap, which can bestored in the drawing commands queue 360. In an alternative embodiment,the drawing commands queue (e.g., 360 of FIG. 3A or 440 of FIG. 4A or4B) may receive the Java graphics API commands from the remote desktopclient adapter and execute the Java graphics API commands to draw intoan off-screen Java bitmap. The HTTP handler (e.g., 344 of FIG. 3A or 422of FIG. 4A) or image conversion module (e.g., 346 of FIG. 3B or 428 ofFIG. 4B) can create an image, such as a joint photographic experts group(JPEG) image, or a portable network graphics (PNG) image, or a bit imagefile (BMP) image or any other image file in an image format suitable forweb browsers, from the Java off-screen bitmap; and the resulting imageis suitable for the browser 312. In one aspect, a JPEG image may bereferred to as a JPEG image file, and a PNG image may be referred to asa PNG image file, and BMP image may be referred to as a BMP image file.In one aspect, as the image (e.g., a JPEG or PNG image) is created inreal time, when it is created, it is simply sent to the web browserwithout being stored at the transcoding server.

In one aspect, the drawing commands queue 360 can serve two purposes:holding or storing the off-screen Java bitmap onto which drawingcommands are executed; and, holding or serving as a drawing coordinatespool, e.g., a queue of coordinates for drawing commands. The drawingcommands queue 360 can, for example, store GDI drawing commandcoordinates received from the remote desktop client adapter. In theevent there are new drawing coordinates in the queue, the drawingcommands queue 360 may send a notification to long polling handlermodule 342 (e.g., can be sent so that any pending request in the drawingrequests queue can be served). The drawing requests queue (e.g., 426 inFIG. 4A or 4B) can function to store incoming long polling drawingrequests from the client and respond to them when there are pendingdrawing commands from the drawing commands queue.

FIG. 3B is a conceptual block diagram of a system 300B including atranscoding server 330 according to certain alternate aspects of thepresent disclosure as used in conjunction with a web browser and aremote machine. System 300B is similar to system 300A of FIG. 3A withsimilar reference numbers, except that the remote desktop client 352 isshown as a separate module/functional block relative to the remotedesktop client 350 adapter, and an image conversion module 346 is shownas a separate module/functional block relative to HTTP handler 344.

FIG. 4A is a detailed conceptual block diagram of a transcoding server400A according to certain aspects of the present disclosure. In oneaspect, transcoding server 400A may preferably be a Java transcodingserver. Transcoding server 400A may include an web application container420 (e.g., a web application container such as a Servlet container), aremote desktop client adapter 430, and a drawing commands queue 440. Theremote desktop client adapter 430 can be configured to interface withany suitable remote desktop client 432 for communication with a remotemachine (e.g., 320 in FIG. 3A or 3B), which may be configured to includea remote desktop server (e.g., 322 in FIG. 3A or 3B). 432. The drawingscommands queue 440 can function as memory or storage that is accessibleby both the web application container 420 and the remote desktop clientadapter 430. The web application container 420 may include an HTTPhandler 422 for handling HTTP requests from a web browser and sendingHTTP responses back to the client/web browser (e.g., 312 in FIG. 3A or3B). In one aspect, the HTTP handler 422 is a standard HTTP handler. Thedrawing commands queue 440 can serve two purposes: holding or storing anoff-screen image, e.g., Java bitmap 444, onto which drawing commands areexecuted; and, serving as a drawing coordinates pool 442, e.g., a queueof coordinates for drawing commands. The coordinates can be those ofregions or areas of an image of the remote desktop that need to beredrawn at the client device to reflect changes on the remote desktop.The areas or regions are sometimes referred to as “dirty” regions, asindicated in FIGS. 4A-4B.

In some embodiments, the web application container may include a longpolling handler module, which includes a long polling handler 424 and adrawing requests queue 426. The long polling handler 424 can operatewith drawing requests queue 426. The drawing requests queue 426 canfunction to store incoming long polling drawing requests received fromthe client (e.g., HTML5 compatible web browser such as web browser 312in FIG. 3A or 3B) via the long polling handler 424 and respond to themwhen there are pending drawing commands from the drawing commands queue440. In one aspect, pending drawing commands may include coordinates forthe image in dirty coordinates pool 442 and/or an image (e.g., Javabitmap 444) in the drawing commands queue 440.

In operation, the web application container 420 may receive and respondto HTTP requests from a web browser on a user device (e.g., 202 in FIG.2A or 310 in FIG. 3A or 3B). The web application container 420 mayprovide user input requests to the remote desktop client adapter 430,which provides a common interface between the web application container420 and the remote desktop client 432. The remote desktop client adapter430 may translate user input information (e.g., mouse, keyboard, andtouch events) into respective remote desktop input calls for the remotedesktop client 432. The remote desktop client adapter 430 may translatethe drawing commands (e.g., GDI drawing commands) of an image of aremote desktop received from a remote machine (e.g., 204 in FIG. 2A or2B or 320 in FIG. 3A or 3B) via a remote desktop display protocol andthe remote desktop client 432, into Java graphics drawing commands.

After receiving and translating the drawing commands from the remotedesktop client 432, the remote desktop client adapter 430 may draw intoan off-screen Java bitmap stored in the drawings commands queue 440 asshown. More specifically, the remote desktop client adapter 430 mayprovide as an image the portion, also referred to as the “dirtyregion(s)” of the remote desktop affected by the user's input from theuser device. Along with the drawing commands, the remote desktop clientadapter 430 may extract, from the drawing command(s), coordinates of thedirty region(s) from the remote desktop client and provide the drawingcoordinates to the drawing commands queue 440 (e.g., dirty coordinatespool 442), as indicated. As explained later, the coordinates can beplaced into an HTTP header section (e.g., by HTTP handler 422) to senddirty region coordinates (e.g., as cookie), along with an image, to abrowser (e.g., 312 in FIG. 3A or 3B) for display.

In the event there are new drawing coordinates in the drawing commandsqueue 440 (e.g., in the dirty coordinates pool 442), drawing commandsqueue 440 may send a notification to the drawing requests queue 426 sothat any pending request in the drawing requests queue 426 can beforwarded to the HTTP handler 422 for serving. The HTTP handler 422 maythen reach to the drawing commands queue 440 (e.g., dirty coordinatespool 442), and obtain the dirty coordinates from the dirty coordinatespool 442. The HTTP handler 422 may then place the dirty coordinates intoan HTTP header section (known as a cookie). In addition, according tothose coordinates, the HTTP handler 422 may obtain an image portion fromthe Java off-screen bitmap 444. The HTTP handler 422 may then send theimage (e.g., as a JPEG image or a PNG image) as well as the coordinates,which are stored in an HTTP response header section, to the web browser(e.g., 312 in FIG. 3A or 3B) for display at the user device's display(e.g., 313 in FIG. 3A or 3B). As a result, the transcoding server 400Acan facilitate a remote desktop session between a user device (e.g., 202in FIG. 2A or 2B or 310 in FIG. 3A or 3B) and a remote machine (e.g.,204 in FIG. 2A or 3B or 320 in FIG. 3A or 3B) without the need for theuser device to utilize proprietary plug-ins or protocols.

In one aspect, an image (or an image file) and drawing coordinates sentby a transcoding server to a web browser may be considered as an exampleof web browser drawing updates. In a preferred aspect, web browserdrawing updates are compatible with the web browser so that the webbrowser can recognize the web browser drawing updates and process themto display an image at the appropriate location on a display. Webbrowser drawing updates may be implemented with other types of drawingdata and commands.

In one aspect, an HTTP protocol (the requests of which may be handledwith an HTTP handler and a long polling handler) between a client deviceand a transcoding server is a pull protocol, and a remote desktopdisplay protocol utilized between a transcoding server and a remotemachine is a push protocol.

Long polling is a modification of the traditional polling technique andcan allow emulation of an information push from a server to a client.With long polling, the client requests information from the server in asimilar way to a normal poll. In the event the server does not have anyinformation available for the client, instead of sending an emptyresponse, the server holds the request and waits for some information tobe available. Once the information becomes available (or after asuitable timeout), a complete response is sent to the client. The clientcan then immediately re-request information from the server, allowingthe server to almost always have an available waiting request that itcan use to deliver data in response to an event.

FIG. 4B is a conceptual block diagram of an alternate transcoding server400B according to certain aspects of the present disclosure. Transcodingserver 400B is similar to transcoding server 400A of FIG. 4A withsimilar drawing numbers, except a separate image conversion orgeneration block 428 is shown. Block 428 may function to take the Javabitmap 444 from the drawing commands queue 440 and convert it to animage file, e.g., JPEG, BMP, PNG, or the like, and provide the imagefile to the HTTP handler 422 so that the HTTP handler 422 can send theimage file along with the associated coordinates to the web browser(e.g., 312 in FIG. 3A or 3B). An additional difference is that theremote desktop client 432 is shown as a separate module/functional blockrelative to the remote desktop client adapter 430.

FIG. 4C is a conceptual block diagram of an image 400C of a remotedesktop of a remote machine. The image 400C can include the entiredesktop of the remote machine. The image may be provided by a remotedesktop client, e.g., 432 in FIG. 4A or 4B, as part of a remote desktopdrawing command for a remote desktop session with a remote machine. Asuitable remote desktop display protocol may be used for the remotedesktop session. Examples can include, but are not limited to, theMicrosoft® Remote Desktop Protocol (RDP), personal computer overinternet protocol (PCoIP), remote FX (RFX) protocol, remote framebuffer(RFB) protocol, Citrix independent computing architecture (ICA), NXprotocol, and/or other suitable remote desktop display protocols. In oneexample, it may be advantageous to use the RDP (which is a push-typeprotocol) as it is widely used. As shown, image 400C can include regionsthat have changed, e.g., image portion 450 and image portion 452,relative to a prior instance of the image of the desktop. Both imageportions 450 and 452 can be provided, along with their coordinates, in adrawing command from an associated remote desktop server to anassociated remote desktop client (to be processed and translated andthen to be sent to a web browser by a transcoding server) for a remotedesktop session. Alternatively, image portion 450 may be provided in adrawing command with its coordinates, and then image portion 452 may beprovided in another drawing command with its coordinates separately(e.g., sequentially). Thus, when only a portion of the remote desktophas changed, then only the changed portion can be provided from a remotedesktop server to its remote desktop client, instead of providing theentire image of the remote desktop to reduce traffic and improveefficiency.

FIG. 5 is a conceptual block diagram and image of a web browser 500according to certain aspects of the present disclosure as used inconjunction with a transcoding server (e.g., 208 in FIG. 2A or 2B, 330in FIG. 3A or 3B, 400A in FIG. 4A, or 400B in FIG. 4B) and a remotemachine (e.g., 204 in FIG. 2A or 2B, or 320 in FIG. 3A or 3B). In apreferred aspect, web browser 500 may be an HTML5 compatible webbrowser. In one aspect, web browser 500 may be web browser 312. Webbrowser 500 can include a script client code 520, for example, aJavaScript client code, and a canvas 530 (e.g., an object or element inmemory supporting 2D drawing or rendering). The script client code 520may refer to a script client 314 in FIG. 3A or 3B. The canvas 530 caninclude or represent the entire viewable window (e.g., 130 of FIG. 1) ofthe browser (e.g., 312, 500). In a preferred aspect, the canvas 530 isan HTML5 compatible canvas, e.g., a canvas element according to theHTML5 specification. Examples of suitable web browsers can include, butare not limited to, Mozilla Firefox, Google Chrome, Safari, and Opera.Web browser 500 may be resident on a suitable user device such as a PCor smartphone or the like.

The script client code 520 can include an input listener 522 responsiveto user inputs such as mouse, keyboard, and touch events. The inputlistener 522 can send HTTP requests with the user inputs to atranscoding server, e.g., server 208 in FIG. 2A or 2B or 330 of FIG. 3Aor 3B. The script client code 520 may also include a load image functionor module 524 that includes an image onload handler 526, which mayextract drawing coordinates from the HTTP header (e.g., from the portionknown as a cookie), draw the received image onto canvas 530, and callthe load image function 524 again, passing it its unique identification(ID). An image on error handler and/or image on abort handler 528 mayalso be included in the load image function 524 to handle loadingerrors. The handler 528 may call the load image function 524. For remotedesktop sessions, the canvas 530 can hold an image of the remote desktopof the remote machine, e.g., 132 of FIG. 1, and the user device maydisplay the image onto a display (e.g., 313 in FIG. 3A or 3B) in theviewable window 130 of the browser (e.g., 312, 500).

As mentioned previously, an HTML5 compatible browser can be used forexemplary embodiments of the present disclosure. HTML5 includes (orsupports) a canvas, which allows for dynamic, real-time, scriptablerendering of 2D shapes and bitmap images. In one aspect, beingscriptable can mean or include reference to utilizing JavaScript forrendering a 2D image. The canvas 530 consists of a drawable regiondefined in HTML code with height and width attributes. JavaScript codemay access the canvas region or area through a full set of drawingfunctions similar to other common 2D APIs, thus allowing for dynamicallygenerated graphics.

In operation, such as accessing a remote machine (e.g., 204 in FIG. 2Aor 2B or 320 in FIG. 3A or 3B)) during a remote desktop session, theinput listener 522 may relay user inputs to the related transcodingserver (e.g., 208 in FIG. 2A or 2B or 330 in FIG. 3A or 3B), whichinterfaces with the remote machine by way of a remote desktop client andremote desktop client adapter, (e.g., 350 in FIG. 3A or 3B or 430 inFIG. 4A or 4B). The script client code 520 can also send a number ofdrawing requests, as indicated by LoadImage(1)-LoadImage(4). Asdescribed previously, the drawing requests can be handled by the relatedtranscoding server as long polling requests.

When drawing commands are received from the remote desktop server viathe remote desktop client, the transcoding server may create/modify anoff-screen image of the remote desktop and provide the actual image andrelated coordinates to the browser 500, where the JavaScript client'simage onload handler (e.g., 528) can then draw the image 532 to thecanvas 530 in accordance with the coordinates extracted from the HTTPheader (e.g., cookie). In one aspect, the image 532 represents a portionof the entire image of the remote desktop that has been changed, andthus the onload handler can receive and update a portion of the canvasbased on the coordinates received (instead of updating the entirecanvas).

In one aspect, a bitmap in a transcoding server (e.g., Java off-screenbitmap 444) may include or represent a bitmap of an entire image of aremote desktop (e.g., 132 of FIG. 1). When a portion(s) of the image ofthe remote desktop is changed (e.g., image portion 450, 452) in responseto, for example, a user's input command or other changes by the remotemachine, the changed image portion(s) and its remote desktop coordinatesmay be provided as a remote desktop drawing command(s) to a remotedesktop client adapter (e.g., 430) from a remote desktop server (e.g.,322) via a remote desktop client (e.g., 432).

In one aspect, the remote desktop client adapter may translate theremote desktop drawing command(s) into a graphics drawing command(s),generate coordinates (corresponding to the remote desktop coordinates)based on the graphics drawing commands, and provide the coordinates intoa pool (e.g., 442). The remote desktop client adapter may execute thegraphics drawing command(s) to draw into the bitmap, or stated inanother way to generate a bitmap portion(s) to update a portion(s) ofthe bitmap (e.g., a portion(s) of 444) according to the coordinatesgenerated by the remote desktop client adapter. The updated portion(s)of the bitmap represents the changed image portion(s) of the remotedesktop. In a preferred aspect, the updated portion(s) of the bitmap isa portion of a Java off-screen bitmap 444.

In one aspect, an HTTP handler (e.g., 422) may form an image filecorresponding to the updated portion(s) of the bitmap, obtain thecoordinates (e.g., from 442) for the image file, and place thecoordinates into a section of an HTTP header. The HTTP handler may thenprovide the image file and the coordinates to a web browser (e.g., 312,500) or more specifically to a script client code (e.g., 520) in asingle HTTP response.

A canvas (e.g., 530) may store the entire image of a remote desktop(e.g., 132 of FIG. 1) to be displayed on a display (e.g., 100, 313) andthen a portion(s) of the canvas 530 may be updated when a portion(s) ofthe image of the remote desktop is changed during a remote desktopsession. In this example, when the script client code receives an imagefile and the coordinates corresponding to the changed portion(s) of theimage of the remote desktop, the script client code can update a portionof the canvas at canvas coordinates corresponding to the coordinatesreceived from the HTTP handler so that the updated portion of the canvasrepresents the image contained in the image file.

Because drawing commands provided by a remote desktop client may includeonly those image portion(s) or region(s) of the remote desktop (withcorresponding coordinates) that have been changed or updated relative toprevious drawing commands, the image provided to the canvas (e.g., 530)can accordingly be limited or minimized to include just the updatedportion(s) of the remote desktop, in exemplary embodiments. The updateson the remote desktop can be due to a user's input (e.g., via a remotedesktop session) or caused by the remote machine itself, e.g., a newindicated time from the system clock. Because the size of the image(s)provided to the canvas (e.g., 530) in response to drawing requests canbe minimized, the traffic for the remote session can be reduced orminimized, facilitating a real time user experience for a remote desktopsession.

In one example, a remote desktop drawing command may comprise a drawingcall such as gdi_bitmap (*data, top, left, width, height, 16, 32) inwhich “*data” may be a pointer to a memory location where the bitmapdata is located. The parameters “top, left, width, height” may representthe coordinates for the bitmap data. The parameter “16” may be thenumber of bits in red-green-blue (RGB), and the parameter “32” may bethe number of bits in alpha-red-green-blue (ARGB). Thus, this exemplarycall indicates where the bitmap data for a portion of the image of theremote desktop (e.g., the portion that has been changed) is located, thecoordinates for the bitmap data, and the number of bits used to convertfrom an RGB format to an ARGB format.

In another example, a graphics drawing command may comprise a drawingcall such as draw-rect (color, top, left, width, height). This drawingcall can draw a rectangle at the coordinates specified by “top, left,width, height” using the specified “color.”

In one aspect, when long polling is utilized between a client device anda transcoding server that uses HTTP (a pull protocol), traffic to theclient device can be reduced to a level experienced by a push-typeprotocol.

FIG. 6 illustrates an example of remote desktop client adapter 600, inaccordance with various aspects of the subject technology. The remotedesktop client adapter 600 facilitates communication between the remotemachine 690, which may include a remote desktop server 680, and the restof the transcoding server components, e.g., the web applicationcontainer (e.g., 420 in FIG. 4A or 4B) and drawing commands queue (e.g.,440 in FIG. 4A or 4B). In some aspects, a remote desktop client adapter600 may provide a common interface between remote desktop client (e.g.,352 in FIG. 3A or 3B, 432 in FIG. 4A or 4B, or 640 in FIG. 6) and webapplication container (e.g., 420 in FIG. 4A or 4B). In some aspects, aremote desktop client adapter 600 may include a drawing command handler630, a remote desktop client manager 610, a user input handler 620, andremote desktop client 640. In some aspects, a remote desktop clientadapter does not necessarily include a remote desktop client 640.Rather, a remote desktop client may be a module separate from remotedesktop client adapter (e.g., as shown in FIG. 3B).

According to various aspects of the subject technology, an adapter 600may include a remote desktop client manager 610, which may be configuredto receive a connection request (e.g., an HTTP request specifying aparticular remote machine) indirectly from a web browser (e.g., 312 inFIG. 3A or 3B) via a web application container (e.g., 340 in FIG. 3A or3B or 420 in FIG. 4A or 4B). In some aspects, a connection request maybe received from a web browser via a web application container thatcommunicates with the web browser. For example, the connection requestcan be received from a web browser via an HTTP handler (e.g., 344 or422) of a web application container. In some aspects, a remote desktopclient manager 620 may manage (or facilitate) establishing a remotedesktop session between a remote desktop client 640 and a remote desktopserver 680 in response to the connection request. For example, a remotedesktop client manager 610 may manage (or facilitate) starting theremote desktop session, passing credentials, settings, preferences,etc., to a remote desktop server (e.g., via a remote desktop client),and stopping the remote desktop session.

In one aspect, a remote desktop client manager 610 may receive aconnection request, e.g., a request originated from a web browser toestablish a connection with remote desktop server (e.g., 322 or 680). Inresponse to the connection request, the remote desktop client manager610 may generate session control commands that are compatible with theremote desktop client, remote desktop server and the remote desktopdisplay protocol, e.g., session control commands that can be understoodand processed by remote desktop client and remote desktop server andthat can be transmitted and received by remote desktop client and remotedesktop server utilizing the remote desktop display protocol. Thesesession control commands may include a command for starting a remotedesktop session, a command for stopping the remote desktop session. Thesession control commands may further include one or more of credentials,settings, preferences, etc. and command(s) for passing credentials,settings, preferences, etc. to remote desktop server (e.g., 322 or 680).In response to the connection HTTP request, the remote desktop clientmanager 610 may further provide the appropriate session controlcommand(s), generated by the remote desktop client manager, to theremote desktop client (e.g., 352 or 640). The remote desktop client maythen use the session control commands received from the remote desktopclient manager 610 to start a remote desktop session with the remotedesktop server, pass credentials, settings, preferences, etc., to remotedesktop server, and stop the remote desktop session.

In one aspect, a remote desktop client manager 610 can translate aconnection request that is not compatible with a remote desktop client,a remote desktop server, or a remote desktop display protocol (e.g.,that cannot be understood or processed by a remote desktop client, aremote desktop server or a remote desktop display protocol) into sessioncontrol commands that are compatible with the remote desktop client, theremote desktop server and the remote desktop display protocol (i.e.,that can be understood and processed by remote desktop client and remotedesktop server and that can be communicated between remote desktopclient and remote desktop server utilizing the remote desktop displayprotocol).

In some aspects, facilitating an establishment of a remote desktopsession, between a remote desktop client and a remote desktop server,comprises generating a session control command based on the initial HTTPrequest. In some aspects, facilitating an establishment of the remotedesktop session comprises transmitting the session control command froma remote desktop client manager 610 to a remote desktop client 640 andthen from the remote desktop client to a remote desktop server 680. Forexample, the session control command may be transmitted to the remotedesktop server 680 via the remote desktop client 640 that communicateswith remote desktop server 680 using a remote desktop display protocol.In some aspects, the remote desktop display protocol comprises at leastone of the Microsoft® Remote Desktop Protocol (RDP), personal computerover internet protocol (PCoIP), remote FX (RFX) protocol, remoteframebuffer (RFB) protocol, independent computing architecture (ICA), NXprotocol, and other suitable remote desktop display protocols. In someaspects, the RFB protocol comprises virtual network computing (VNC).

According to certain aspects of the subject technology, a server such asserver 208, 330, 400A, 400B (e.g., via a remote desktop client manager610) can maintain open connections between its remote desktop client andone or more remote desktop servers at all times, allowing single ormultiple client devices to be interactively connected and disconnectedto remote desktop sessions instantly. In some aspects, remote desktopsessions may never need to be disconnected from the one or more remotedesktop servers, as a server can maintain active connections to the oneor more remote desktop servers. Of course, a remote machine (e.g., 690)may go down for reasons that are outside of a related transcodingserver's control; however, the connection can be maintained as long asthe remote machine is available for remote access. For example, a remotedesktop client manager 610 may continuously maintain the remote desktopsession until the remote desktop server disconnects from the remotedesktop session depending on the remote desktop server's idle remoteconnection settings. In some aspects, remote desktop sessionsestablished utilizing a remote desktop client manager 610 may be resizedand adjusted for best display and user experience to utilize the fullcapability of the client devices.

According to various aspects of the subject technology, a user inputhandler 620 may receive an input request indirectly from a web browsersuch as a server 208, 330, 400A, 400B (e.g., via an HTTP handler 344 or422), and convert the input request into a format recognized by and/orcompatible with remote desktop client 640 and remote desktop server 680.For example, user input handler 620 receives an input request that wastransmitted utilizing a request-response protocol from web browser. Inpreferred aspects, the request-response protocol may comprise hypertexttransfer protocol (HTTP). In another aspect, the request-responseprotocol may comprise other suitable request-response protocols. In someaspects, the input request is received from a web browser (e.g., 312 inFIG. 3A or 3B) via a web application container (e.g., 340 420) thatcommunicates with the web browser. For example, the input request isreceived via an HTTP handler (e.g., 344 or 422) of a web applicationcontainer. In some aspects, the input request comprises at least one ofa mouse event, a keyboard event, and a touch event. User input handler620 may translate the input request that is in a format suitable for orcompatible with the request-response protocol into an input command(e.g., a remote desktop display protocol input command) that is suitablefor or compatible the remote desktop display protocol. The user inputhandler 620 may transmit the input command to a remote desktop client640, which may transmit the input command to a remote desktop server680. For example, user input handler 620 may facilitate transmitting theinput command to remote desktop server 680 via remote desktop client 640that communicates with remote desktop server 680 using the remotedesktop display protocol. In one aspect, an input request is sometimesreferred to as a user input command and vice versa. Please note,however, if an input request is referred to as an input command when itis received via HTTP, it is a HTTP request rather than a command. In oneaspect, an input command is sometimes referred to as an input call or aremote desktop input command and vice versa.

A remote machine 690 (e.g., its remote desktop server 680) may executeone or more actions based on the input command and send drawing data, asa result of the executed one or more actions, to a server such as atranscoding server 208, 330, 400A or 400B (e.g., a remote desktop client620 of the server). According to various aspects, a remote desktopclient 640 can receive a screen drawing command transmitted from aremote machine 690 (e.g., its remote desktop server 680) utilizing theremote desktop display protocol, in response to the input commandtransmitted to remote machine 690 (e.g., its remote desktop server 680).In one aspect, a screen drawing command received from a remote machinemay be sometimes referred to as a drawing command, a remote machinedrawing command, or a remote desktop drawing command received from aremote machine and vice versa. The drawing command handler 630 may thenreceive the screen drawing command from the remote desktop client 640connected to the remote machine 690. For example, a drawing commandhandler 630 can receive the screen drawing command from a remote machine690 (e.g., its remote desktop server 680) via a remote desktop client640 that communicates with the remote machine 690 (e.g., its remotedesktop server 680) using the remote desktop display protocol.

According to certain aspects, a drawing command handler 630 may converta screen drawing command into a format recognized by and/or compatiblewith a web browser (e.g., 312 in FIG. 3A or 3B). For example, a drawingcommand handler 630 may translate a screen drawing command that issuitable for or compatible with a remote desktop client, a remotedesktop server and a remote desktop display protocol, into a graphicsdrawing command that is compatible with the server 208, 330, 400A or400B, such as a Java graphics (abstract window toolkit) API command whenthe server is a Java transcoding server. In some aspects, translatingthe screen drawing command can include calculating new, and/or adjustingreceived drawing command parameters, and/or making adjustments to thereceived bitmap data, such as, but not limited to, converting the 16-bitred-green-blue (RGB) 5-6-5 color format into a 32-bitalpha-red-green-blue (ARGB) 8-8-8-8 format. In some aspects, drawingcommand handler 630 may execute the graphics drawing command (e.g., Javagraphics API command) to draw into an already created image bitmap,(e.g., the off-screen Java bitmap 444) of the drawing commands queue(e.g., 360 in FIG. 3A or 3B, or 440 in FIG. 4A or 4B) at the transcodingserver (e.g., 330 in FIG. 3A or 3B, 400A in FIG. 4A, or 400B in FIG.4B). In one aspect, Java graphics API command is sometimes referred toas Java graphics command or Java graphics drawing command. In oneaspect, the off-screen bitmap may be a storage or memory location thatis a part of a drawing commands queue (e.g., 360 or 440) accessible byan application container (e.g., 340 or 420). In one aspect, the size ofan off-screen bitmap may represent the size of a remote session. Statedin another way, the size of an off-screen bitmap may represent the sizeof the remote desktop, or an off-screen bitmap may be a bitmaprepresentation of an entire image of a remote desktop.

Preferred embodiments of the present disclosure may, in essence,translate a request in HTTP to a command in a remote desktop displayprotocol and vice versa (e.g., translate requests/responsestransmitted/received via HTTP to commands transmitted/received via aremote desktop display protocol, and vice versa) for a remote sessionbetween a client device and a remote machine. For example, the inputrequest from the web browser such as a server 208, 330, 400A, 400B maybe translated into the input command (e.g., a remote desktop inputcommand) that is suitable for or compatible with the remote desktopdisplay protocol and is received by remote desktop server 680 via remotedesktop client 640. The screen drawing command transmitted from theremote machine 690 (e.g., in response to the input command) utilizingthe remote desktop display protocol may be translated into the graphicsdrawing command that is compatible with the server 208, 330, 400A or400B, such as a Java graphics (abstract window toolkit) API command. Insome aspects, HTTP is a pull protocol while a remote desktop displayprotocol may be a push protocol. In some aspects, a drawing command inpush protocol may be translated into a drawing update (or a drawingresponse) in pull protocol during a remote session between a clientdevice and a remote machine.

With continued reference to FIG. 6, a drawing command handler 630, whendrawing into the off-screen bitmap, may transmit pixel data to theoff-screen bitmap. In some aspects, the pixel data is used to update aportion of the off-screen bitmap (e.g., an off-screen Java bitmap). Insome aspects, a drawing command handler 630 may transmit the pixel datato the off-screen bitmap so that the updated portion of the off-screenbitmap may be stored and/or converted to an image file.

According to certain aspects, a drawing command handler 630 can generateone or more coordinates corresponding to the updated portion of theoff-screen bitmap (e.g., an image drawn into the off-screen bitmap whenthe graphics drawing command is executed). For example, the one or morecoordinates may identify the locations where the corresponding imagebitmap is to be executed on the canvas of a web browser. In one example,the one or more coordinates may be extracted or copied from the graphicsdrawing command. A drawing command handler 630 may also transmit the oneor more coordinates to a dirty coordinates pool 442 in FIG. 4A or 4Bthat is a part of a drawing commands queue (e.g., 360 or 440). In someaspects, a drawing command handler 630 may transmit the one or morecoordinates to the dirty coordinates pool so that the one or morecoordinates may be stored in the dirty coordinates pool. Thus, a drawingcommand handler 630 may update “dirty” region coordinates in the drawingcommands queue. In some aspects, a drawing command handler 630 maytransmit a notification signal to a drawing requests queue (e.g., 426 inFIG. 4A or 4B) of a web application container (e.g., 420). In someaspects, the notification signal/message may indicate that the that theimage bitmap (e.g., the off-screen Java bitmap) has been updated.

FIG. 7 is a sequence diagram 700 of the interactions between atranscoding server (e.g., 208, 330, 400A or 400B) as used in conjunctionwith a web browser (e.g., 312) and a remote machine (e.g., 204, 320 or690), according to certain aspects of the present disclosure. Thesequences are shown as 701-724. As shown at 701, a web browser can sendan initial HTTP request to a transcoding server (e.g., transcodingserver 400A of FIG. 4), for example, to its HTTP handler (e.g., 422).The initial HTTP request can include a URL that specifies a desiredremote machine. At 702 and 703, the transcoding server can facilitateestablishing a remote desktop connection with the remote machine (e.g.,its remote desktop server). At 704, the transcoding server also canprovide a client code, e.g., JavaScript client code, to the web browser.The JavaScript client code in the web browser can generate a number ofdrawing requests, which can be handled by the transcoding server as longpolling requests. In exemplary embodiments, four drawing requests may bepending at any one time although the number can be selected as desiredand optimized for different implementations.

As shown at the bottom of the diagram, e.g., at 719 and 722, the webbrowser can provide user input requests (as HTTP requests) to thetranscoding server, which in turn, e.g., at 721 and 724, can provide theuser input commands to the remote machine, e.g., for control of theremote desktop of the remote machine. At 705, the remote machine canprovide drawing commands (one command is shown) to the drawing commandsqueue (e.g., 360 or 440) in the transcoding server by way of the remotedesktop client adapter (e.g., 350, 430 or 600), which draws acorresponding image of the remote desktop into the off-screen bitmap inthe drawing commands queue. In response to the drawing command, thedrawing commands queue can provide, at 706, notification to the drawingrequests queue (e.g., 426) in the long polling handler module (e.g.,342) of the transcoding server. In response, the first pending drawingrequest can be taken from the drawing requests queue and provided to theHTTP handler. In response, at 707 and 708, the HTTP handler may obtainthe image from the drawing commands queue. At 709, the HTTP handler mayprovide the image and corresponding coordinates in a response sent tothe script client (e.g., 314 or 520, or more specifically 526) of theweb browser. The script client may then, at 711, draw the image (e.g.,532) to the canvas (e.g., 316 or 530) using the appropriate coordinates,extracted from the cookie, for displaying the remote desktop in the webbrowser.

In one aspect, an HTTP handler (e.g., 422) is a standard HTTP handler inthat when it receives a request from a web browser, it responds withoutwaiting or storing the request. For example, when an HTTP handlerreceives a user input request as a HTTP request at 719 or 722 from a webbrowser, the HTTP handler responds immediately with a null response at720 and 723, respectively (while the request is sent to the remotemachine via a remote desktop client adapter). In one aspect, a longpolling handler (e.g., 424) may be used to receive a request and respondto it based on an event, and a long polling request may be stored. Forexample, under one condition (e.g., a drawing command is pending), thenthe request is responded immediately (e.g., the polling handler sendsthe drawing request to the HTTP handler so that the HTTP handler cansend a response to the drawing request immediately. Under anothercondition (e.g., a drawing command is not pending), then the request maybe stored away (e.g., into a drawing requests queue) until a conditionis satisfied (e.g., a new drawing command has arrived at a drawingcommands queue).

In one aspect, a remote desktop is a desktop of a remote machine. In oneaspect, during a remote desktop session with a remote machine, a webbrowser of a client device may access, control and/or view any or allapplications and files resident on the remote machine. In anotheraspect, during a remote desktop session with a remote machine, dependingon the user's credentials and settings, a web browser may be allowed toaccess, control and/or view some of the applications and files residenton the remote machine.

In one preferred aspect, each of a client device, a transcoding server,and a remote machine is a separate and distinct machine that is remotefrom one another. In one aspect, a transcoding server may be a machinethat can communicate with one or more client devices and one or moreremote machines, and a transcoding server may be a machine that cancommunicate over a web. In one aspect, a web browser may be anapplication that allows a user to retrieve, present or communicateinformation over a web.

FIG. 8 is a conceptual block diagram illustrating an example of acomputing system 800 useful for embodiments of the present disclosure.System 800 may be, for example, a client device (e.g., 202 or 310), aserver (e.g., 208, 330, 400A or 400B) or a remote machine (e.g., 204,320 or 690). The system 800 may include a processing system 802. Theprocessing system 802 is capable of communication with a receiver 806and a transmitter 808 through a bus 804 or other structures or devices.It should be understood that communication means other than busses canbe utilized with the disclosed configurations. The processing system 802can generate audio, video, multimedia, and/or other types of data to beprovided to the transmitter 809 for communication. In addition, audio,video, multimedia, and/or other types of data can be received at thereceiver 806, and processed by the processing system 802.

The processing system 802 may include a general-purpose processor or aspecific-purpose processor for executing instructions and may furtherinclude a machine-readable medium 819, such as a volatile ornon-volatile memory, for storing data and/or instructions for softwareprograms. The instructions, which may be stored in a machine-readablemedium 810 and/or 819, may be executed by the processing system 802 tocontrol and manage access to the various networks, as well as provideother communication and processing functions. The instructions may alsoinclude instructions executed by the processing system 802 for varioususer interface devices, such as a display 812 and a keypad 814. Theprocessing system 802 may include an input port 822 and an output port824. Each of the input port 822 and the output port 824 may include oneor more ports. The input port 822 and the output port 824 may be thesame port (e.g., a bi-directional port) or may be different ports.

The processing system 802 may be implemented using software, hardware,or a combination of both. By way of example, the processing system 102may be implemented with one or more processors. A processor may be ageneral-purpose microprocessor, a microcontroller, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a programmable logic device (PLD),a controller, a state machine, gated logic, discrete hardwarecomponents, and/or any other suitable device that can performcalculations or other manipulations of information.

A machine-readable medium can be one or more machine-readable media.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Instructions may include code (e.g., in source code format, binary codeformat, executable code format, or any other suitable format of code).

Machine-readable media (e.g., 819) may include storage integrated into aprocessing system, such as might be the case with an applicationspecific integrated circuit (ASIC). Machine-readable media (e.g., 810)may also include storage external to a processing system, such as arandom access memory (RAM), a flash memory, a read only memory (ROM), aprogrammable read-only memory (PROM), an erasable PROM (EPROM),registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any othersuitable storage device. In addition, machine-readable media may includea transmission line or a carrier wave that encodes a data signal. Thoseskilled in the art will recognize how best to implement the describedfunctionality for the processing system 802. According to one aspect ofthe disclosure, a machine-readable medium is a computer-readable mediumencoded or stored with instructions and is a computing element, whichdefines structural and functional interrelationships between theinstructions and the rest of the system, which permit the instructions'functionality to be realized. In one aspect, a machine-readable mediumis a non-transitory machine-readable medium, a machine-readable storagemedium, or a non-transitory machine-readable storage medium. In oneaspect, a computer-readable medium is a non-transitory computer-readablemedium, a computer-readable storage medium, or a non-transitorycomputer-readable storage medium. Instructions may be executable, forexample, by a client device, a server, a remote machine, or by aprocessing system of a client device, a server, or a remote machine.Instructions can be, for example, a computer program including code.

An interface 816 may be any type of interface and may reside between anyof the components shown in FIG. 8. An interface 816 may also be, forexample, an interface to the outside world (e.g., an Internet networkinterface). A transceiver block 807 may represent one or moretransceivers, and each transceiver may include a receiver 806 and atransmitter 809. A functionality implemented in a processing system 802may be implemented in a portion of a receiver 806, a portion of atransmitter 809, a portion of a machine-readable medium 810, a portionof a display 812, a portion of a keypad 814, or a portion of aninterface 816, and vice versa.

FIG. 9A illustrates a block diagram representing a method 900 ofaccessing and controlling a remote desktop from a web browser (e.g., 312or 500) via a transcoding server (e.g., 208, 330, 400A or 400B)according to certain aspects of the present disclosure. FIG. 9Billustrates a continuation of the method 900. For method 900, a webbrowser having 2D rendering capabilities, e.g., an HTML5 compatible webbrowser, is provided, as described at 902. Input requests can bereceived at the transcoding server for controlling the remote desktop,as described at 906. The input requests can be translated from theprotocol of the web browser, e.g., preferably HTTP, into the protocol ofthe remote desktop server associated with the remote desktop, asdescribed at 908. The input commands can then be provided to the remotemachine (which may include a remote desktop server) as described at 910.

Referring to FIG. 9B and continuing with the description of method 900,drawing commands and coordinates, e.g., of dirty regions, can bereceived by the transcoding server from the remote desktop server, asdescribed at 912. In response, the drawing commands and coordinates canbe translated from the protocol of the remote desktop server to theprotocol of the web browser, as described at 914. The transcoding servercan respond by drawing or generating an image of the remote desktop, asdescribed at 916. The image and the corresponding coordinates can belinked or unionized, as described at 918. A drawing request from the webbrowser can be responded to, as described at 920, by sending the imageand coordinates to the web browser for display, as described at 922.Accordingly, method 900 may be used for controlling and accessing aremote desktop session via HTTP, and such control can be in real-time.

An exemplary embodiment of a method of accessing and controlling aremote desktop of a remote machine (e.g., 204, 320 or 690) from a webbrowser (e.g., 312 or 500) via a transcoding server (e.g., 208, 330,400A or 400B) may include the following three steps: step one can happenonce, at the beginning of a session; and steps two and three cancontinue interchangeably during the remote desktop session.

The first step can include an initial HTTP request by the web browser(e.g., a connection request to connect to a remote machine). Forexample, an initial HTTP request is sent by the web browser, preferablyan HTML5 compatible browser. The web browser receives back a response,which can contain a script client such as 314 or 500, e.g., JavaScriptAjax client code. The transcoding server (e.g., Java transcoding server)can use the connection request to establish a connection to a remotemachine via a remote desktop client. A remote desktop client on or usedwith the Java transcoding server can establish the connection to aremote machine, which utilizes a remote desktop display protocol. Thetranscoding server can function to interface between the HTTP protocoland the remote desktop display protocol. In one aspect, between the webbrowser and the transcoding server, there is no connection, as HTTP is aconnectionless protocol. Instead, there are only separate requests andresponses in HTTP protocol.

The second step is remote session drawing at the web browser: On thebrowser side, the client JavaScript code can continuously re-send anumber of, e.g., four asynchronous (Ajax) HTTP requests to find out ifthere are any “dirty” regions of the remote desktop of the remotemachine to (re)draw. On the Java transcoding server, these drawingrequests are handled as long polling requests, meaning that they will beresponded to only if there is data to be drawn, otherwise they hang inthe drawing requests queue (e.g., 426). Also, on the Java transcodingserver, the remote session is drawn into an off-screen Java bitmap in adrawing commands queue of the transcoding server. In addition, thecoordinates of the drawing command are also appended or added to thedrawing commands queue. This last part also sends a notification to thedrawing requests queue of the transcoding server, so that the firstwaiting request from the drawing requests queue can be served. In HTTPresponse to the browser, the “dirty” drawing image is sent, togetherwith the drawing coordinates that are stored in one of the HTTP headersections (known as a cookie). On the browser side, the script clientreceives the “dirty” image and the coordinates, and the script clientdraws the image into an HTML canvas (e.g., 530) using coordinates fromthe cookie. This allows the remote session from a remote machine (e.g.,an image of the remote desktop of the remote machine) to be drawn, via aJava transcoding server, to the client's HTML5 browser.

The third step involves a user input, such as a mouse click, keystroke,or touch event. On the browser side, the script client detects, e.g., amouse event, and sends an HTTP request to the transcoding server,passing along the X and Y coordinates of the event. The Java transcodingserver receives the request, sends an empty reply (see, e.g., 720 and723 in FIG. 7) to close the HTTP request, and then via remote desktopclient adapter, it forwards this request to the remote desktop client,which sends it via its protocol to the remote machine. These user inputrequests can be handled in a standard way, i.e., not as long pollingevents, to receive and process user input. User input can then be sentto the remote machine.

In a preferred aspect, a script client is not installed on the clientdevice. In other words, a script client does not exist (and is notpre-installed) on the web browser or on the client device prior to thefirst step described above (e.g., prior to the web browser connectingto, or sending a request to connect to, the transcoding server toinitiate a remote session with a remote machine). In a preferred aspect,a client device simply needs a web browser to initiate accessing andcontrolling a remote desktop of a remote machine or to initiate a remotedesktop session with the remote machine. Thus, the client device doesnot need software or a browser plug-in for a remote desktop displayprotocol. The transcoding server provides the script client in real timeto the web browser via HTTP once the web browser requests a connectionto a remote machine for a remote desktop session. The web browser'sconnection to the remote machine is established through the transcodingserver, and the script client is deleted from the client device and theweb browser when the remote desktop session is terminated or the browseris closed.

Illustration of Method/Apparatus/Machine Readable Storage Medium forFacilitating Accessing and Controlling a Remote Desktop of a RemoteMachine in Real Time by a Web Browser at a Client Device Via a HypertextTransfer Protocol (Http) Utilizing a Transcoding Server (Described asClauses)

The subject technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the subjecttechnology are described as numbered clauses (1, 2, 3, etc.) forconvenience. These are provided as examples, and do not limit thesubject technology. Clause 1 below is presented, for example, withreference to the figures of the present disclosure, e.g., FIGS. 10A-10C,etc. It is noted that any of the dependent clauses may be combined inany combination, and placed into a respective independent clause, e.g.,clauses 1, 11, and 22. The other clauses can be presented in a similarmanner.

1. A method (see, e.g., method 1000-A of FIG. 10A) of facilitatingaccessing and controlling a remote desktop of a remote machine (see,e.g., 320 of FIG. 3A) in real time by a web browser (see, e.g., 500 ofFIG. 5) at a client device (see, e.g., 310 in FIG. 3A) via a hypertexttransfer protocol (HTTP) utilizing a transcoding server (see, e.g., 330of FIG. 3A, the method comprising:

receiving, at the transcoding server, a remote desktop drawing commandbased on an image of the remote desktop of the remote machine, whereinthe remote desktop drawing command is compatible with a remote desktopdisplay protocol utilized by the remote machine (see, e.g., item 1002-Ain FIG. 10A);

translating, at the transcoding server, the remote desktop drawingcommand into a web browser drawing update that is compatible with theweb browser (see, e.g., item 1004-A in FIG. 10A); and

facilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device utilizingHTTP during a remote desktop session between the client device and theremote machine (see, e.g., item 1006-A in FIG. 10A),

wherein the remote desktop display protocol is a push protocol (see,e.g., item 1008-A in FIG. 10A),

wherein HTTP is a pull protocol (see, e.g., item 1010-A in FIG. 10A).

2. The method of clause 1, wherein the web browser drawing updatecomprises an image file and drawing coordinates for the image file thatare recognizable and processable by the web browser.

3. The method of clause 1, wherein the translating comprises:

translating the remote desktop drawing command into a Java graphicsdrawing command;

updating a portion of a Java bitmap using the Java graphics drawingcommand, wherein the updated portion of the Java bitmap represents aportion of an entire image of the remote desktop;

creating an image file from the Java bitmap; and

generating drawing coordinates for the image file,

wherein the web browser drawing update comprises the image file and thedrawing coordinates for the image file,

wherein the facilitating providing comprises placing the drawingcoordinates into an HTTP header,

wherein utilizing HTTP comprises using an HTTP handler,

wherein the transcoding server is a Java transcoding server that isconfigured to provide an application framework for hosting one or moreweb applications.

4. The method of clause 1, wherein the translating comprises:

translating the remote desktop drawing command into a graphics drawingcommand that is compatible with the transcoding server, wherein thegraphics drawing command includes coordinates;

extracting the coordinates from the graphics drawing command;

updating at least a portion of an off-screen bitmap based on thegraphics drawing command,

wherein the at least a portion of the off-screen bitmap is associatedwith the coordinates,

wherein the off-screen bitmap is based on the image of the remotedesktop;

creating an image file based on the at least a portion of the off-screenbitmap; and

wherein the web browser drawing update comprises the image file and thecoordinates.

5. The method of clause 1, wherein the web browser is an HTML5compatible web browser.

6. The method of clause 1, further comprising:

receiving a user input request from the web browser, using HTTP;

translating the user input request into an input command compatible withthe remote desktop display protocol; and

providing the input command to the remote desktop client for accessingand controlling the remote desktop of the remote machine during theremote desktop session,

wherein the web browser drawing update comprises an image file anddrawing coordinates for the image file that are recognizable andprocessable by the web browser,

wherein the image file and the drawing coordinates represent a portionof an entire image of the remote desktop that has been changed inresponse to the input command.

7. The method of clause 6, wherein the user input request comprises atleast one of a mouse event, a keyboard event, and a touch event.

8. The method of clause 1, wherein the remote desktop drawing commandcomprises remote desktop drawing command parameters and bitmap datareceived from a remote desktop server of the remote machine,

wherein the translating comprises one or more of: calculating newdrawing command parameters based on the remote desktop drawing commandparameters; adjusting the remote desktop drawing command parameters; andmaking adjustments to the bitmap data.

9. The method of clause 1, wherein the remote desktop drawing commandcomprises remote desktop drawing command parameters and bitmap datareceived from a remote desktop server of the remote machine,

wherein the translating comprises making adjustments to the bitmap data,

wherein the making adjustments comprises converting a 16-bitred-green-blue (RGB) 5-6-5 color format into a 32-bitalpha-red-green-blue (ARGB) 8-8-8-8 format.

10. The method of clause 1, wherein the transcoding server is anintermediary between the remote machine and the client device, andwherein the transcoding server is physically separate from the remotemachine.

11. A machine-readable storage medium (see, e.g., machine-readablestorage medium 1000-B of FIG. 10B) encoded with instructions executableby a processing system to perform a method of facilitating accessing andcontrolling a remote desktop of a remote machine (see, e.g., 320 of FIG.3A) in real time by a web browser (see, e.g., 500 of FIG. 5) at a clientdevice (see, e.g., 310 of FIG. 3A) via a hypertext transfer protocol(HTTP) utilizing a transcoding server (see, e.g., 330 of FIG. 3A), theinstructions comprising code for:

receiving, at the transcoding server, a remote desktop drawing commandbased on an image of the remote desktop of the remote machine, whereinthe remote desktop drawing command is compatible with a remote desktopdisplay protocol utilized by the remote machine (see, e.g., item 1002-Bin FIG. 10B);

translating, at the transcoding server, the remote desktop drawingcommand into a web browser drawing update that is compatible with theweb browser (see, e.g., item 1004-A in FIG. 10B); and

facilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device using HTTPduring a remote desktop session between the client device and the remotemachine (see, e.g., item 1006-A in FIG. 10B),

wherein the remote desktop display protocol is a push protocol (see,e.g., item 1008-A in FIG. 10B), and

wherein HTTP is a pull protocol (see, e.g., item 1010-A in FIG. 10B).

12. The machine-readable storage medium of clause 11, wherein the webbrowser drawing update comprises an image file and drawing coordinatesfor the image file that are recognizable and processable by the webbrowser.

13. The machine-readable storage medium of clause 11, wherein thetranslating comprises:

translating the remote desktop drawing command into a Java graphicsdrawing command;

updating a portion of a Java bitmap using the Java graphics drawingcommand, wherein the updated portion of the Java bitmap represents aportion of an entire image of the remote desktop;

creating an image file from the Java bitmap; and

generating drawing coordinates for the image file,

wherein the web browser drawing update comprises the image file and thedrawing coordinates for the image file,

wherein the facilitating providing comprises placing the drawingcoordinates into an HTTP header,

wherein utilizing HTTP comprises using an HTTP handler,

wherein the transcoding server is a Java transcoding server that isconfigured to provide an application framework for hosting one or moreweb applications.

14. The machine-readable storage medium of clause 11, wherein thetranslating comprises:

translating the remote desktop drawing command into a graphics drawingcommand that is compatible with the transcoding server, wherein thegraphics drawing command includes coordinates;

extracting the coordinates from the graphics drawing command;

updating at least a portion of an off-screen bitmap based on thegraphics drawing command,

wherein the at least a portion of the off-screen bitmap is associatedwith the coordinates,

wherein the off-screen bitmap is based on the image of the remotedesktop;

creating an image file based on the at least a portion of the off-screenbitmap; and

wherein the web browser drawing update comprises the image file and thecoordinates.

15. The machine-readable storage medium of clause 11, wherein the webbrowser is an HTML5 compatible web browser.

16. The machine-readable storage medium of clause 11, wherein theinstructions further comprise code for:

receiving a user input request from the web browser, using HTTP;

translating the user input request into an input command compatible withthe remote desktop display protocol; and

providing the input command to the remote desktop client for accessingand controlling the remote desktop of the remote machine during theremote desktop session;

wherein the web browser drawing update comprises an image file anddrawing coordinates for the image file that are recognizable andprocessable by the web browser; and

wherein the image file and the drawing coordinates represent a portionof an entire image of the remote desktop that has been changed inresponse to the input command.

17. The machine-readable storage medium of clause 16, wherein the userinput request comprises at least one of a mouse event, a keyboard event,and a touch event.

18. The machine-readable storage medium of clause 11, wherein the remotedesktop drawing command comprises remote desktop drawing commandparameters and bitmap data received from a remote desktop server of theremote machine,

wherein the translating comprises one or more of: calculating newdrawing command parameters based on the remote desktop drawing commandparameters; adjusting the remote desktop drawing command parameters; andmaking adjustments to the bitmap data.

19. The machine-readable storage medium of clause 11, wherein the remotedesktop drawing command comprises remote desktop drawing commandparameters and bitmap data received from a remote desktop server of theremote machine,

wherein the translating comprises making adjustments to the bitmap data,

wherein the making adjustments comprises converting a 16-bitred-green-blue (RGB) 5-6-5 color format into a 32-bitalpha-red-green-blue (ARGB) 8-8-8-8 format.

20. The machine-readable storage medium of clause 11, wherein thetranscoding server is an intermediary between the remote machine and theclient device, and wherein the transcoding server is physically separatefrom the remote machine.

21. A computing machine comprising the machine-readable storage mediumof clause 11, wherein the computing machine is the transcoding server.

22. An apparatus for facilitating accessing and controlling a remotedesktop of a remote machine (see, e.g., 320 of FIG. 3A) in real time bya web browser (see, 500 of FIG. 5) at a client device (see, e.g., 310 ofFIG. 3A) via a hypertext transfer protocol (HTTP) utilizing atranscoding server (see, e.g., 330 of FIG. 3A), the apparatuscomprising:

means for receiving a remote desktop drawing command based on an imageof the remote desktop of the remote machine, wherein the remote desktopdrawing command is compatible with a remote desktop display protocolutilized by the remote machine (see, e.g., item 1002-C in FIG. 10C);

means for translating the remote desktop drawing command into a webbrowser drawing update that is compatible with the web browser (see,e.g., item 1004-C in FIG. 10C); and means for facilitating providing theweb browser drawing update from the transcoding server to the webbrowser of the client device utilizing HTTP during a remote desktopsession between the client device and the remote machine (see, e.g.,item 1006-C in FIG. 10C);

wherein the remote desktop display protocol is a push protocol (see,e.g., item 1008-C in FIG. 10C); and

wherein HTTP is a pull protocol (see, e.g., item 1010-C in FIG. 10C).

23. The apparatus of clause 22, wherein the web browser drawing updatecomprises an image file and drawing coordinates for the image file thatare recognizable and processable by the web browser.

24. The apparatus of clause 22, wherein the means for translatingcomprises:

means for translating the remote desktop drawing command into a Javagraphics drawing command;

means for updating a portion of a Java bitmap using the Java graphicsdrawing command, wherein the updated portion of the Java bitmaprepresents a portion of an entire image of the remote desktop;

means for creating an image file from the Java bitmap; and

means for generating drawing coordinates for the image file,

wherein the web browser drawing update comprises the image file and thedrawing coordinates for the image file,

wherein the means for facilitating providing comprises means for placingthe drawing coordinates into an HTTP header,

wherein utilizing HTTP comprises utilizing an HTTP handler, and

wherein the transcoding server is a Java transcoding server that isconfigured to provide an application framework for hosting one or moreweb applications.

25. The apparatus of clause 22, wherein the means for translatingcomprises:

means for translating the remote desktop drawing command into a graphicsdrawing command that is compatible with the transcoding server, whereinthe graphics drawing command includes coordinates;

means for extracting the coordinates from the graphics drawing command;

means for updating at least a portion of an off-screen bitmap based onthe graphics drawing command, wherein the at least a portion of theoff-screen bitmap is associated with the coordinates, wherein theoff-screen bitmap is based on the image of the remote desktop; and

means for creating an image file based on the at least a portion of theoff-screen bitmap;

wherein the web browser drawing update comprises the image file and thecoordinates.

26. The apparatus of clause 22, wherein the web browser is an HTML5compatible web browser.

27. The apparatus of clause 22, further comprising:

means for receiving a user input request from the web browser, usingHTTP;

means for translating the user input request into an input commandcompatible with the remote desktop display protocol; and

means for providing the input command to the remote desktop client foraccessing and controlling the remote desktop of the remote machineduring the remote desktop session;

wherein the web browser drawing update comprises an image file anddrawing coordinates for the image file that are recognizable andprocessable by the web browser; and

wherein the image file and the drawing coordinates represent a portionof an entire image of the remote desktop that has been changed inresponse to the input command.

28. The apparatus of clause 27, wherein the user input request comprisesat least one of a mouse event, a keyboard event, and a touch event.

29. The apparatus of clause 22, wherein the remote desktop drawingcommand comprises remote desktop drawing command parameters and bitmapdata received from a remote desktop server of the remote machine,

wherein the means for translating comprises one or more of: means forcalculating new drawing command parameters based on the remote desktopdrawing command parameters; means for adjusting the remote desktopdrawing command parameters; and means for making adjustments to thebitmap data.

30. The apparatus of clause 22, wherein the remote desktop drawingcommand comprises remote desktop drawing command parameters and bitmapdata received from a remote desktop server,

wherein the means for translating comprises means for making adjustmentsto the bitmap data of the remote machine,

wherein the means for making adjustments comprises means for convertinga 16-bit red-green-blue (RGB) 5-6-5 color format into a 32-bitalpha-red-green-blue (ARGB) 8-8-8-8 format.

31. The apparatus of clause 22, wherein the transcoding server is anintermediary between the remote machine and the client device, andwherein the transcoding server is physically separate from the remotemachine.

32. The apparatus of clause 22, wherein the apparatus comprises thetranscoding server.

33. The apparatus of clause 22, wherein the apparatus comprises aprocessing system and a memory.

Illustration of Method/Apparatus/Machine Readable Storage Medium forFacilitating Conducting a Remote Desktop Session Between a Web Browserof a Client Device and a Remote Machine Via a Transcoding Server in RealTime and Utilizing Hypertext Markup Language that Supports aTwo-Dimensional (2D) Canvas and Dynamic Drawing (Described as Clauses).

The subject technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the subjecttechnology are described as numbered clauses (1, 2, 3, etc.) forconvenience. These are provided as examples, and do not limit thesubject technology. Clause 1 below is presented, for example, withreference to FIGS. 11A-11C. It is noted that any of the dependentclauses may be combined in any combination, and placed into a respectiveindependent clause, e.g., clauses 1, 11, and 22. The other clauses canbe presented in a similar manner.

1. A method (see, e.g., item 1100-A in FIG. 11A) of facilitatingconducting a remote desktop session between a web browser of a clientdevice (see, e.g., 310 in FIG. 3A) and a remote machine (see, e.g., 320)via a transcoding server (see, e.g., 330) in real time and utilizinghypertext markup language that supports a two-dimensional (2D) canvasand dynamic drawing, the method comprising:

receiving, at the transcoding server, a user input request from the webbrowser at the client device for access and control of the remotemachine, wherein the web browser supports a 2D canvas and dynamicdrawing (see, e.g., item 1102-A in FIG. 11A);

translating, at the transcoding server, the user input request into aninput command compatible with a remote desktop display protocol to beutilized by the transcoding server for facilitating communication withthe remote machine (see, e.g., item 1104-A in FIG. 11A);

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote machine in response to the input command (see, e.g.,item 1106-A in FIG. 11A);

translating, at the transcoding server, the remote desktop drawingcommand into a drawing update compatible with the hypertext markuplanguage (see, e.g., item 1108-A in FIG. 11A); and

facilitating providing the drawing update from the transcoding server tothe web browser (see, e.g., item 1110-A in FIG. 11A);

wherein the transcoding server is an intermediary between the remotemachine and the client device, and wherein the transcoding server isphysically separate from the remote machine.

2. The method of clause 1, wherein the translating the remote desktopdrawing command comprises:

-   -   translating the remote desktop drawing command into a Java        graphics drawing command;    -   executing the Java graphics drawing command to update a portion        of a Java bitmap, wherein the Java bitmap represents an entire        image of a remote desktop of the remote machine;    -   generating coordinates for the updated portion of the Java        bitmap based on the Java graphics drawing command;    -   forming an image file based on the updated portion of the Java        bitmap, wherein the image file is compatible with HTML5; and    -   obtaining drawing coordinates for the image file based on the        coordinates for the updated portion of the Java bitmap, wherein        the drawing coordinates are compatible with HTML5,

wherein the drawing update comprises the image file and the drawingcoordinates for the image file,

wherein the drawing update represents a portion of the entire image ofthe remote desktop,

wherein the web browser temporarily comprises JavaScript client codeduring the remote desktop session while the remote desktop sessionpersists;

wherein the method further comprises receiving, at the transcodingserver, drawing requests from the JavaScript client code of the webbrowser,

wherein the facilitating providing the drawing update comprisesfacilitating providing the drawing update from the transcoding server tothe JavaScript client code of the web browser in response to one of thedrawing requests from the JavaScript client code of the web browser.

3. The method of clause 1, wherein the translating the remote desktopdrawing command comprises:

-   -   translating the remote desktop drawing command into a graphics        drawing command compatible with the transcoding server;    -   updating a portion of a bitmap based on the graphics drawing        command, wherein the updated portion of the bitmap represents a        portion of an entire image of a remote desktop of the remote        machine that has changed relative to a previous graphics drawing        command;    -   generating coordinates for the updated portion of the bitmap;    -   forming an image file based on the updated portion of the        bitmap, wherein the image file is HTML5 compatible; and    -   obtaining drawing coordinates for the image file, wherein the        drawing coordinates are compatible with HTML5,

wherein the drawing update comprises the image file and the drawingcoordinates for the image file,

wherein the method further comprises receiving, at the transcodingserver, drawing requests from the web browser,

wherein the facilitating providing the drawing update comprisesfacilitating providing the drawing update from the transcoding server tothe web browser in response to one of the drawing requests from the webbrowser.

4. The method of clause 1, wherein the transcoding server comprises aremote desktop client adapter configured to translate the user inputrequest into the input command compatible with the remote desktopdisplay protocol and to translate the remote desktop drawing commandinto the graphics drawing command.

5. The method of clause 1, further comprising receiving long pollingHTTP requests from the web browser, wherein the long polling HTTPrequests comprise drawing requests.

6. The method of clause 1, further comprising receiving from the webbrowser an initial HTTP request comprising a uniform resource locator(URL) of the remote machine.

7. The method of clause 6, further comprising facilitating providing ascript client code to the web browser in response to the initial HTTPrequest for the URL of the remote machine, wherein the script clientcode is compatible with HTML5.

8. The method of clause 1, wherein the remote desktop drawing command iscompatible with the remote desktop display protocol, wherein the remotedesktop display protocol is a push protocol, and wherein thefacilitating providing the drawing update comprises facilitatingproviding the drawing update using HTTP that is a pull protocol.

9. The method of clause 1, wherein dynamic drawing comprises drawing inreal time a portion of the 2D canvas, rather than drawing the entire 2Dcanvas, in response to one or more drawing requests of a script clientof the web browser.

10. The method of clause 1, wherein the 2D canvas is updatable by aportion at a time according to a set of coordinates.

11. A machine-readable storage medium (see, e.g., 810, 819 in FIG. 8)encoded with instructions executable by a processing system (see, e.g.,802) to perform a method of facilitating conducting a remote desktopsession between a web browser of a client device (see, e.g., 310 in FIG.3A) and a remote machine (see, e.g., 320) via a transcoding server (see,e.g., 330) in real time and utilizing hypertext markup language thatsupports a two-dimensional (2D) canvas and dynamic drawing, theinstructions comprising code for:

receiving, at the transcoding server, a user input request from the webbrowser at the client device for access and control of the remotemachine, wherein the web browser supports a 2D canvas and dynamicdrawing (see, e.g., item 1102-B in FIG. 11B);

translating, at the transcoding server, the user input request into aninput command compatible with a remote desktop display protocol to beutilized by the transcoding server for facilitating communication withthe remote machine (see, e.g., item 1104-B in FIG. 11B);

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote machine in response to the input command (see, e.g.,item 1106-B in FIG. 11B);

translating, at the transcoding server, the remote desktop drawingcommand into a drawing update compatible with the hypertext markuplanguage (see, e.g., item 1108-B in FIG. 11B); and

facilitating providing the drawing update from the transcoding server tothe web browser (see, e.g., item 1110-B in FIG. 11B);

wherein the transcoding server is an intermediary between the remotemachine and the client device, and wherein the transcoding server isphysically separate from the remote machine.

12. The machine-readable storage medium of clause 11, wherein thetranslating the remote desktop drawing command comprises:

-   -   translating the remote desktop drawing command into a Java        graphics drawing command;    -   executing the Java graphics drawing command to update a portion        of a Java bitmap, wherein the Java bitmap represents an entire        image of a remote desktop of the remote machine;    -   generating coordinates for the updated portion of the Java        bitmap based on the Java graphics drawing command;    -   forming an image file based on the updated portion of the Java        bitmap, wherein the image file is compatible with HTML5; and    -   obtaining drawing coordinates for the image file based on the        coordinates for the updated portion of the Java bitmap, wherein        the drawing coordinates are compatible with HTML5,

wherein the drawing update comprises the image file and the drawingcoordinates for the image file,

wherein the drawing update represents a portion of the entire image ofthe remote desktop,

wherein the web browser temporarily comprises JavaScript client codeduring the remote desktop session while the remote desktop sessionpersists;

wherein the method further comprises receiving, at the transcodingserver, drawing requests from the JavaScript client code of the webbrowser,

wherein the facilitating providing the drawing update comprisesfacilitating providing the drawing update from the transcoding server tothe JavaScript client code of the web browser in response to one of thedrawing requests from the JavaScript client code of the web browser.

13. The machine-readable storage medium of clause 11, wherein thetranslating the remote desktop drawing command comprises:

-   -   translating the remote desktop drawing command into a graphics        drawing command compatible with the transcoding server;    -   updating a portion of a bitmap based on the graphics drawing        command, wherein the updated portion of the bitmap represents a        portion of an entire image of a remote desktop of the remote        machine that has changed relative to a previous graphics drawing        command;    -   generating coordinates for the updated portion of the bitmap;    -   forming an image file based on the updated portion of the        bitmap, wherein the image file is HTML5 compatible; and    -   obtaining drawing coordinates for the image file, wherein the        drawing coordinates are compatible with HTML5,

wherein the drawing update comprises the image file and the drawingcoordinates for the image file,

wherein the method further comprises receiving, at the transcodingserver, drawing requests from the web browser, and

wherein the facilitating providing the drawing update comprisesfacilitating providing the drawing update from the transcoding server tothe web browser in response to one of the drawing requests from the webbrowser.

14. The machine-readable storage medium of clause 11, wherein thetranscoding server comprises a remote desktop client adapter configuredto translate the user input request into the input command compatiblewith the remote desktop display protocol and to translate the remotedesktop drawing command into the graphics drawing command.

15. The machine-readable storage medium of clause 11, further comprisingcode for receiving long polling HTTP requests from the web browser,wherein the long polling HTTP requests comprise drawing requests.

16. The machine-readable storage medium of clause 11, further comprisingcode for receiving from the web browser an initial HTTP requestcomprising a uniform resource locator (URL) of the remote machine.

17. The machine-readable storage medium of clause 16, further comprisingcode for facilitating providing a script client code to the web browserin response to the initial HTTP request for the URL of the remotemachine, wherein the script client code is compatible with HTML5.

18. The machine-readable storage medium of clause 11, wherein the remotedesktop drawing command is compatible with the remote desktop displayprotocol, wherein the remote desktop display protocol is a pushprotocol, and wherein the facilitating providing the drawing updatecomprises facilitating providing the drawing update using HTTP that is apull protocol.

19. The machine-readable storage medium of clause 11, wherein dynamicdrawing comprises drawing in real time a portion of the 2D canvas,rather than drawing the entire 2D canvas, in response to one or moredrawing requests of a script client of the web browser.

20. The machine-readable storage medium of clause 11, wherein the 2Dcanvas is updatable by a portion at a time according to a set ofcoordinates.

21. A computing machine comprising the machine-readable storage mediumof clause 11, wherein the computing machine is the transcoding server.

22. An apparatus (see, e.g., item 1100-C in FIG. 11C) for facilitatingconducting a remote desktop session between a web browser of a clientdevice (see, e.g., 310 in FIG. 3A) and a remote machine (see, e.g., 320)via a transcoding server (see, e.g., 330) in real time and utilizinghypertext markup language that supports a two-dimensional (2D) canvasand dynamic drawing, the apparatus comprising:

means for receiving a user input request from the web browser at theclient device for access and control of the remote machine, wherein theweb browser supports a 2D canvas and dynamic drawing (see, e.g., item1102-C in FIG. 11C);

means for translating the user input request into an input commandcompatible with a remote desktop display protocol to be utilized by thetranscoding server for facilitating communication with the remotemachine (see, e.g., item 1104-C in FIG. 11C);

means for receiving a remote desktop drawing command from the remotemachine in response to the input command (see, e.g., item 1106-C in FIG.11C);

means for translating the remote desktop drawing command into a drawingupdate compatible with the hypertext markup language (see, e.g., item1108-C in FIG. 11C); and

means for facilitating providing the drawing update from the transcodingserver to the web browser (see, e.g., item 1110-C in FIG. 11C);

wherein the transcoding server is an intermediary between the remotemachine and the client device, and wherein the transcoding server isphysically separate from the remote machine.

23. The apparatus of clause 22, wherein the means for translating theremote desktop drawing command comprises:

-   -   means for translating the remote desktop drawing command into a        Java graphics drawing command;    -   means for executing the Java graphics drawing command to update        a portion of a Java bitmap, wherein the Java bitmap represents        an entire image of a remote desktop of the remote machine;    -   means for generating coordinates for the updated portion of the        Java bitmap based on the Java graphics drawing command;    -   means for forming an image file based on the updated portion of        the Java bitmap, wherein the image file is compatible with        HTML5; and    -   means for obtaining drawing coordinates for the image file based        on the coordinates for the updated portion of the Java bitmap,        wherein the drawing coordinates are compatible with HTML5,

wherein the drawing update comprises the image file and the drawingcoordinates for the image file,

wherein the drawing update represents a portion of the entire image ofthe remote desktop,

wherein the web browser temporarily comprises JavaScript client codeduring the remote desktop session while the remote desktop sessionpersists,

wherein the apparatus further comprises means for receiving drawingrequests from the JavaScript client code of the web browser,

wherein the means for facilitating providing the drawing updatecomprises means for facilitating providing the drawing update from thetranscoding server to the JavaScript client code of the web browser inresponse to one of the drawing requests from the JavaScript client codeof the web browser.

24. The apparatus of clause 22, wherein the means for translating theremote desktop drawing command comprises:

-   -   means for translating the remote desktop drawing command into a        graphics drawing command compatible with the transcoding server;    -   means for updating a portion of a bitmap based on the graphics        drawing command, wherein the updated portion of the bitmap        represents a portion of an entire image of a remote desktop of        the remote machine that has changed relative to a previous        graphics drawing command;    -   means for generating coordinates for the updated portion of the        bitmap;    -   means for forming an image file based on the updated portion of        the bitmap, wherein the image file is HTML5 compatible; and    -   means for obtaining drawing coordinates for the image file,        wherein the drawing coordinates are compatible with HTML5,

wherein the drawing update comprises the image file and the drawingcoordinates for the image file,

wherein the apparatus further comprises means for receiving drawingrequests from the web browser,

wherein the means for facilitating providing the drawing updatecomprises means for facilitating providing the drawing update from thetranscoding server to the web browser in response to one of the drawingrequests from the web browser.

25. The apparatus of clause 22, wherein the transcoding server comprisesa remote desktop client adapter configured to translate the user inputrequest into the input command compatible with the remote desktopdisplay protocol and to translate the remote desktop drawing commandinto the graphics drawing command.

26. The apparatus of clause 22, further comprising means for receivinglong polling HTTP requests from the web browser, wherein the longpolling HTTP requests comprise drawing requests.

27. The apparatus of clause 22, further comprising means for receivingfrom the web browser an initial HTTP request comprising a uniformresource locator (URL) of the remote machine.

28. The apparatus of clause 27, further comprising means forfacilitating providing a script client code to the web browser inresponse to the initial HTTP request for the URL of the remote machine,wherein the script client code is compatible with HTML5.

29. The apparatus of clause 22, wherein the remote desktop drawingcommand is compatible with the remote desktop display protocol, whereinthe remote desktop display protocol is a push protocol, and wherein themeans for facilitating providing the drawing update comprises means forfacilitating providing the drawing update using HTTP that is a pullprotocol.

30. The apparatus of clause 22, wherein dynamic drawing comprisesdrawing in real time a portion of the 2D canvas, rather than drawing theentire 2D canvas, in response to one or more drawing requests of ascript client of the web browser.

31. The apparatus of clause 22, wherein the 2D canvas is updatable by aportion at a time according to a set of coordinates.

32. The apparatus of clause 22, wherein the apparatus comprises thetranscoding server.

33. The apparatus of clause 22, wherein the apparatus comprises aprocessing system and a memory.

Illustration of Method/Apparatus/Machine Readable Storage Medium forFacilitating a Remote Desktop Session Between a Web Browser of a ClientDevice and a Remote Machine Through a Transcoding Server, UtilizingHypertext Transfer Protocol (Http) Headers of Http for Remote DesktopSession Drawing (Described as Clauses).

The subject technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the subjecttechnology are described as numbered clauses (1, 2, 3, etc.) forconvenience. These are provided as examples, and do not limit thesubject technology. It is noted that any of the dependent clauses may becombined in any combination, and placed into a respective independentclause, e.g., clauses 1, 11, and 22. Clause 1 below is presented, forexample, with reference to FIGS. 12A-12C. The other clauses can bepresented in a similar manner.

1. A method (see, e.g., item 1200-A in FIG. 12A) of facilitating aremote desktop session between a web browser of a client device (see,e.g., 310 in FIG. 3A) and a remote machine (see, e.g., 320) through atranscoding server (see, e.g., 330), utilizing hypertext transferprotocol (HTTP) headers of HTTP for remote desktop session drawing, themethod comprising:

receiving, at the transcoding server, drawing requests from the webbrowser at the client device (see, e.g., item 1202-A in FIG. 12A);

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote machine using a remote desktop display protocol, whereinthe remote desktop drawing command is based on an image of a remotedesktop of the remote machine (see, e.g., item 1204-A in FIG. 12A);

translating, at the transcoding server, the remote desktop drawingcommand into a display image and drawing coordinates for the displayimage (see, e.g., item 1206-A in FIG. 12A);

placing, at the transcoding server, the drawing coordinates into an HTTPresponse header (see, e.g., item 1208-A in FIG. 12A); and

in response to at least one of the drawing requests, facilitatingproviding the display image and the drawing coordinates together to theweb browser in a single HTTP response, for drawing the display image ofthe remote desktop at the web browser, wherein the single HTTP responsecomprises the HTTP response header (see, e.g., item 1210-A in FIG. 12A),

wherein the remote desktop display protocol is a push protocol, and

wherein HTTP is a pull protocol.

2. The method of clause 1, wherein the translating comprises:

translating the remote desktop drawing command into a Java graphicsdrawing command, wherein the transcoding server comprises a Javacompatible web application container;

updating a portion of a Java graphics bitmap of the remote desktop inresponse to the Java graphics drawing command;

generating coordinates for the updated portion of the Java bitmap fromthe Java graphics drawing command;

generating the display image compatible with the web browser based onthe updated portion of the Java bitmap; and

obtaining the drawing coordinates for the display image based on thecoordinates for the updated portion of the Java bitmap,

wherein the display image and the drawing coordinates are compatiblewith HTML,

wherein the updated portion of the Java graphics bitmap represents aportion of an entire image of the remote desktop of the remote machine,

wherein the display image and the drawing coordinates represent theportion of the entire image of the remote desktop of the remote machine.

3. The method of clause 1, wherein the translating comprises:

translating the remote desktop drawing command into a graphics drawingcommand compatible with the transcoding server;

updating a portion of a bitmap of the remote desktop based on thegraphics drawing command;

generating the coordinates for the updated portion of the bitmap;

generating the display image compatible with the web browser based onthe updated portion of the bitmap; and

obtaining the drawing coordinates for the display image,

wherein the display image and the drawing coordinates are compatiblewith HTML.

4. The method of clause 1, wherein the display image and the drawingcoordinates are compatible with HTML5.

5. The method of clause 1, wherein the transcoding server is anintermediary between the remote machine and the client device, andwherein the transcoding server is physically separate from the remotemachine.

6. The method of clause 1, wherein the remote desktop drawing commandcomprises coordinates of a region of the remote desktop that has changedrelative to a previous remote desktop drawing command.

7. The method of clause 6, wherein the coordinates specify a redrawingregion.

8. The method of clause 1, wherein the drawing coordinates arecompatible with JavaScript client code of the web browser, and whereinthe display image is compatible with HTML of the web browser.

9. The method of clause 1, wherein the display image comprises a scaledimage of the remote desktop.

10. The method of clause 1, wherein the display image comprises anoffset image of the remote desktop.

11. A machine-readable storage medium (see, e.g., 810, 819 in FIG. 8)encoded with instructions executable by a processing system (see, e.g.,802) to perform a method of facilitating a remote desktop sessionbetween a web browser of a client device (see, e.g., 310 in FIG. 3A) anda remote machine (see, e.g., 320) through a transcoding server (see,e.g., 330), utilizing hypertext transfer protocol (HTTP) headers of HTTPfor remote desktop session drawing, the instructions comprising codefor:

receiving, at the transcoding server, drawing requests from the webbrowser at the client device (see, e.g., item 1202-B in FIG. 12B);

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote machine using a remote desktop display protocol, whereinthe remote desktop drawing command is based on an image of a remotedesktop of the remote machine (see, e.g., item 1204-B in FIG. 12B);

translating, at the transcoding server, the remote desktop drawingcommand into a display image and drawing coordinates for the displayimage (see, e.g., item 1206-B in FIG. 12B);

placing, at the transcoding server, the drawing coordinates into an HTTPresponse header (see, e.g., item 1208-B in FIG. 12B); and

in response to at least one of the drawing requests, facilitatingproviding the display image and the drawing coordinates together to theweb browser in a single HTTP response, for drawing the display image ofthe remote desktop at the web browser, wherein the single HTTP responsecomprises the HTTP response header (see, e.g., item 1210-B in FIG. 12B),

wherein the remote desktop display protocol is a push protocol, and

wherein HTTP is a pull protocol.

12. The machine-readable storage medium of clause 11, wherein thetranslating comprises:

translating the remote desktop drawing command into a Java graphicsdrawing command, wherein the transcoding server comprises a Javacompatible web application container;

updating a portion of a Java graphics bitmap of the remote desktop inresponse to the Java graphics drawing command;

generating coordinates for the updated portion of the Java bitmap fromthe Java graphics drawing command;

generating the display image compatible with the web browser based onthe updated portion of the Java bitmap; and

obtaining the drawing coordinates for the display image based on thecoordinates for the updated portion of the Java bitmap,

wherein the display image and the drawing coordinates are compatiblewith HTML,

wherein the updated portion of the Java graphics bitmap represents aportion of an entire image of the remote desktop of the remote machine,

wherein the display image and the drawing coordinates represent theportion of the entire image of the remote desktop of the remote machine.

13. The machine-readable storage medium of clause 11, wherein thetranslating comprises:

translating the remote desktop drawing command into a graphics drawingcommand compatible with the transcoding server;

updating a portion of a bitmap of the remote desktop based on thegraphics drawing command;

generating the coordinates for the updated portion of the bitmap;

generating the display image compatible with the web browser based onthe updated portion of the bitmap; and

obtaining the drawing coordinates for the display image,

wherein the display image and the drawing coordinates are compatiblewith HTML.

14. The machine-readable storage medium of clause 11, wherein thedisplay image and the drawing coordinates are compatible with HTML5.

15. The machine-readable storage medium of clause 11, wherein thetranscoding server is an intermediary between the remote machine and theclient device, and wherein the transcoding server is physically separatefrom the remote machine.

16. The machine-readable storage medium of clause 11, wherein the remotedesktop drawing command comprises coordinates of a region of the remotedesktop that has changed relative to a previous remote desktop drawingcommand.

17. The machine-readable storage medium of clause 16, wherein thecoordinates specify a redrawing region.

18. The machine-readable storage medium of clause 11, wherein thedrawing coordinates are compatible with JavaScript client code of theweb browser, and wherein the display image is compatible with HTML ofthe web browser.

19. The machine-readable storage medium of clause 11, wherein thedisplay image comprises a scaled image of the remote desktop.

20. The machine-readable storage medium of clause 11, wherein thedisplay image comprises an offset image of the remote desktop.

21. A computing machine comprising the machine-readable storage mediumof clause 11, wherein the computing machine is the transcoding server.

22. An apparatus (see, e.g., item 1200-C in FIG. 12C) for facilitating aremote desktop session between a web browser of a client device (see,e.g., 310 in FIG. 3A) and a remote machine (see, e.g., 320) through atranscoding server (see, e.g., 330), utilizing hypertext transferprotocol (HTTP) headers of HTTP for remote desktop session drawing, theapparatus comprising:

means for receiving drawing requests from the web browser at the clientdevice (see, e.g., item 1202-C in FIG. 12C);

means for receiving a remote desktop drawing command from the remotemachine using a remote desktop display protocol, wherein the remotedesktop drawing command is based on an image of a remote desktop of theremote machine (see, e.g., item 1204-C in FIG. 12C);

means for translating the remote desktop drawing command into a displayimage and drawing coordinates for the display image (see, e.g., item1206-C in FIG. 12C);

means for placing the drawing coordinates into an HTTP response header(see, e.g., item 1208-C in FIG. 12C); and

means for, in response to at least one of the drawing requests,facilitating providing the display image and the drawing coordinatestogether to the web browser in a single HTTP response, for drawing thedisplay image of the remote desktop at the web browser, wherein thesingle HTTP response comprises the HTTP response header (see, e.g., item1210-C in FIG. 12C),

wherein the remote desktop display protocol is a push protocol, and

wherein HTTP is a pull protocol.

23. The apparatus of clause 22, wherein the means for translatingcomprises:

means for translating the remote desktop drawing command into a Javagraphics drawing command, wherein the transcoding server comprises aJava compatible web application container;

means for updating a portion of a Java graphics bitmap of the remotedesktop in response to the Java graphics drawing command;

means for generating coordinates for the updated portion of the Javabitmap from the Java graphics drawing command;

means for generating the display image compatible with the web browserbased on the updated portion of the Java bitmap; and

means for obtaining the drawing coordinates for the display image basedon the coordinates for the updated portion of the Java bitmap,

wherein the display image and the drawing coordinates are compatiblewith HTML,

wherein the updated portion of the Java graphics bitmap represents aportion of an entire image of the remote desktop of the remote machine,

wherein the display image and the drawing coordinates represent theportion of the entire image of the remote desktop of the remote machine.

24. The apparatus of clause 22, wherein the means for translatingcomprises:

means for translating the remote desktop drawing command into a graphicsdrawing command compatible with the transcoding server;

means for updating a portion of a bitmap of the remote desktop based onthe graphics drawing command;

means for generating the coordinates for the updated portion of thebitmap;

means for generating the display image compatible with the web browserbased on the updated portion of the bitmap; and

means for obtaining the drawing coordinates for the display image,

wherein the display image and the drawing coordinates are compatiblewith HTML.

25. The apparatus of clause 22, wherein the display image and thedrawing coordinates are compatible with HTML5.

26. The apparatus of clause 22, wherein the transcoding server is anintermediary between the remote machine and the client device, andwherein the transcoding server is physically separate from the remotemachine.

27. The apparatus of clause 22, wherein the remote desktop drawingcommand comprises coordinates of a region of the remote desktop that haschanged relative to a previous remote desktop drawing command.

28. The apparatus of clause 27, wherein the coordinates specify aredrawing region.

29. The apparatus of clause 22, wherein the drawing coordinates arecompatible with JavaScript client code of the web browser, and whereinthe display image is compatible with HTML of the web browser.

30. The apparatus of clause 22, wherein the display image comprises ascaled image of the remote desktop.

31. The apparatus of clause 22, wherein the display image comprises anoffset image of the remote desktop.

32. The apparatus of clause 22, wherein the apparatus comprises thetranscoding server.

33. The apparatus of clause 22, wherein the apparatus comprises aprocessing system and a memory.

Illustration of Method/Apparatus/Machine Readable Storage Medium forFacilitating a Remote Desktop Session Between a Web Browser of a ClientDevice and a Remote Machine Through a Transcoding Server, Utilizing LongPolling to Reduce Traffic to the Client Device (Described as Clauses).

The subject technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the subjecttechnology are described as numbered clauses (1, 2, 3, etc.) forconvenience. These are provided as examples, and do not limit thesubject technology. It is noted that any of the dependent clauses may becombined in any combination, and placed into a respective independentclause, e.g., clauses 1, 11, and 22. Clause 1 below is presented, forexample, with reference to FIGS. 13A-13C. The other clauses can bepresented in a similar manner.

1. A method (see, e.g., 1300-A of FIG. 13A) of facilitating a remotedesktop session between a web browser (see, e.g., 500 of FIG. 5) of aclient device (see, e.g., 310 of FIG. 3A) and a remote machine (see,e.g., 320 of FIG. 3A) through a transcoding server (see, e.g., 330 ofFIG. 3A), utilizing long polling to reduce traffic to the client device,the method comprising:

receiving, at the transcoding server, a plurality of drawing requestsfrom the web browser at the client device, using HTTP, wherein HTTP is apull protocol (see, e.g., item 1302-A in FIG. 13A);

handling, at the transcoding server, the plurality of drawing requestsas long polling requests (see, e.g., item 1304-A in FIG. 13A);

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote machine (see, e.g., item 1306-A in FIG. 13A);

translating, at the transcoding server, the remote desktop drawingcommand into a web browser drawing update, wherein the remote desktopdrawing command is compatible with a push protocol, wherein the webbrowser drawing update is compatible with HTTP, wherein HTTP is a pullprotocol (see, e.g., item 1308-A in FIG. 13A); and

facilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device, utilizingHTTP, as a response to at least one of the plurality of drawing requestsfrom the web browser (see, e.g., item 1310-A in FIG. 13A).

2. The method of clause 1, wherein the handling comprises:

determining whether a drawing command is pending at the transcodingserver for the web browser;

if there is no pending drawing command, then storing the plurality ofdrawing requests in a drawing requests queue as long poling requests;and

if there is a pending drawing command, then providing at least one ofthe plurality of drawing requests to an HTTP handler in the transcodingserver to allow the HTTP handler to serve the pending drawing command inresponse to the at least one of the plurality of drawing requests.

3. The method of clause 1, wherein the remote desktop drawing commandrepresents a portion of an entire image of a remote desktop of theremote machine,

wherein the translating comprises:

-   -   translating the remote desktop drawing command into a Java        graphics drawing command;    -   updating a portion of a Java bitmap of the entire image of the        remote desktop in response to the Java graphics drawing command;    -   generating coordinates of the updated portion of the Java bitmap        based on the Java graphics drawing command;    -   generating an image file based on the updated portion of the        Java bitmap, wherein the image file is compatible with the web        browser; and    -   obtaining drawing coordinates for the image file based on the        coordinates of the updated portion of the Java bitmap,

wherein the web browser drawing update comprises the image file and thedrawing coordinates.

4. The method of clause 3, wherein the handling comprises:

determining whether a drawing command is pending at the transcodingserver for the web browser;

if there is no pending drawing command, then storing the plurality ofdrawing requests in a drawing requests queue as long poling requests;and

if there is a pending drawing command, then providing at least one ofthe plurality of drawing requests to an HTTP handler in the transcodingserver to allow the HTTP handler to serve the pending drawing command inresponse to the at least one of the plurality of drawing requests.

5. The method of clause 4, wherein the facilitating providing comprises:

placing, at the HTTP handler, the drawing coordinates into an HTTPheader of a single HTTP transmission response to the web browser; and

including, at the HTTP handler, the image file into the single HTTPtransmission response to the web browser to facilitate providing theimage file and the drawing coordinates together to the web browser inthe single HTTP transmission response.

6. The method of clause 5, further comprising:

when a drawing commands queue has new coordinates, sending anotification to the drawing requests queue to allow at least one of theplurality of drawing requests in the drawing requests queue to beforwarded to the HTTP handler.

7. The method of clause 1, further comprising:

receiving a new drawing request from the web browser, in response tofacilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device as a responseto the at least one of the plurality of drawing requests from the webbrowser.

8. The method of clause 1, further comprising:

receiving a request from the web browser to connect to the remotemachine; and facilitating providing a JavaScript client code to the webbrowser in response to the request to connect to the remote machine,

wherein the receiving the plurality of drawing requests comprisesreceiving the plurality of drawing requests from the JavaScript clientcode,

wherein the facilitating providing the web browser drawing updatecomprises facilitating providing the web browser drawing update to theJavaScript client code.

9. The method of clause 8, further comprising: facilitating deleting theJavaScript client code from the web browser when the remote desktopsession is terminated.

10. The method of clause 1, further comprising:

receiving, at the transcoding server, a user input request from the webbrowser for accessing or controlling a remote desktop of the remotemachine,

translating, at the transcoding server, the user input request into aninput command compatible with the push protocol;

facilitating providing the input command to the remote machine utilizingthe push protocol,

wherein the receiving the remote desktop drawing command comprisesreceiving the remote desktop drawing command in response to the inputcommand.

11. A machine-readable storage medium (see, e.g., item 1300-B in FIG.13B) encoded with instructions executable by a processing system toperform a method of facilitating a remote desktop session between a webbrowser (see, e.g., 500 of FIG. 5) of a client device (see, e.g., 310 ofFIG. 3A) and a remote machine (see, e.g., 320 of FIG. 3B) through atranscoding server (see, e.g., 330 of FIG. 3B), utilizing long pollingto reduce traffic to the client device, the instructions comprising codefor:

receiving, at the transcoding server, a plurality of drawing requestsfrom the web browser at the client device, using HTTP, wherein HTTP is apull protocol (see, e.g., item 1302-B in FIG. 13B);

handling, at the transcoding server, the plurality of drawing requestsas long polling requests (see, e.g., item 1304-B in FIG. 13B);

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote machine (see, e.g., item 1306-B in FIG. 13B);

translating, at the transcoding server, the remote desktop drawingcommand into a web browser drawing update, wherein the remote desktopdrawing command is compatible with a push protocol, wherein the webbrowser drawing update is compatible with HTTP, wherein HTTP is a pullprotocol (see, e.g., item 1308-B in FIG. 13B); and

facilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device, utilizingHTTP, as a response to at least one of the plurality of drawing requestsfrom the web browser (see, e.g., item 1310-B in FIG. 13B).

12. The machine-readable storage medium of clause 11, wherein thehandling comprises:

determining whether a drawing command is pending at the transcodingserver for the web browser;

if there is no pending drawing command, then storing the plurality ofdrawing requests in a drawing requests queue as long poling requests;and

if there is a pending drawing command, then providing at least one ofthe plurality of drawing requests to an HTTP handler in the transcodingserver to allow the HTTP handler to serve the pending drawing command inresponse to the at least one of the plurality of drawing requests.

13. The machine-readable storage medium of clause 11, wherein the remotedesktop drawing command represents a portion of an entire image of aremote desktop of the remote machine,

wherein the translating comprises:

-   -   translating the remote desktop drawing command into a Java        graphics drawing command;    -   updating a portion of a Java bitmap of the entire image of the        remote desktop in response to the Java graphics drawing command;    -   generating coordinates of the updated portion of the Java bitmap        based on the Java graphics drawing command;    -   generating an image file based on the updated portion of the        Java bitmap, wherein the image file is compatible with the web        browser; and    -   obtaining drawing coordinates for the image file based on the        coordinates of the updated portion of the Java bitmap,

wherein the web browser drawing update comprises the image file and thedrawing coordinates.

14. The machine-readable storage medium of clause 13, wherein thehandling comprises:

determining whether a drawing command is pending at the transcodingserver for the web browser;

if there is no pending drawing command, then storing the plurality ofdrawing requests in a drawing requests queue as long poling requests;and

if there is a pending drawing command, then providing at least one ofthe plurality of drawing requests to an HTTP handler in the transcodingserver to allow the HTTP handler to serve the pending drawing command inresponse to the at least one of the plurality of drawing requests.

15. The machine-readable storage medium of clause 14, wherein thefacilitating providing comprises:

placing, at the HTTP handler, the drawing coordinates into an HTTPheader of a single HTTP transmission response to the web browser; and

including, at the HTTP handler, the image file into the single HTTPtransmission response to the web browser to facilitate providing theimage file and the drawing coordinates together to the web browser inthe single HTTP transmission response.

16. The machine-readable storage medium of clause 15, further comprisingcode for:

when a drawing commands queue has new coordinates, sending anotification to the drawing requests queue to allow at least one of theplurality of drawing requests in the drawing requests queue to beforwarded to the HTTP handler.

17. The machine-readable storage medium of clause 11, further comprisingcode for:

receiving a new drawing request from the web browser, in response tofacilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device as a responseto the at least one of the plurality of drawing requests from the webbrowser.

18. The machine-readable storage medium of clause 11, further comprisingcode for:

receiving a request from the web browser to connect to the remotemachine; and facilitating providing a JavaScript client code to the webbrowser in response to the request to connect to the remote machine,

wherein the receiving the plurality of drawing requests comprisesreceiving the plurality of drawing requests from the JavaScript clientcode,

wherein the facilitating providing the web browser drawing updatecomprises facilitating providing the web browser drawing update to theJavaScript client code.

19. The machine-readable storage medium of clause 18, further comprisingcode for: facilitating deleting the JavaScript client code from the webbrowser when the remote desktop session is terminated.

20. The machine-readable storage medium of clause 11, further comprisingcode for:

receiving, at the transcoding server, a user input request from the webbrowser for accessing or controlling a remote desktop of the remotemachine,

translating, at the transcoding server, the user input request into aninput command compatible with the push protocol;

facilitating providing the input command to the remote machine utilizingthe push protocol,

wherein the receiving the remote desktop drawing command comprisesreceiving the remote desktop drawing command in response to the inputcommand.

21. A computing machine comprising the machine-readable storage mediumof clause 11, wherein the computing machine is the transcoding server.

22. An apparatus (see, e.g., item 1300-C in FIG. 13C) for facilitating aremote desktop session between a web browser (see, e.g., 500 of FIG. 5)of a client device (see, e.g., 310 in FIG. 3A) and a remote machine(see, e.g., 330 in FIG. 3A) through a transcoding server (see, e.g., 330in FIG. 3A), utilizing long polling to reduce traffic to the clientdevice, the apparatus comprising:

means for receiving a plurality of drawing requests from the web browserat the client device, using HTTP, wherein HTTP is a pull protocol (see,e.g., item 1302-C in FIG. 13C);

means for handling the plurality of drawing requests as long pollingrequests (see, e.g., item 1304-C in FIG. 13C);

means for receiving a remote desktop drawing command from the remotemachine (see, e.g., item 1306-C in FIG. 13C);

means for translating the remote desktop drawing command into a webbrowser drawing update, wherein the remote desktop drawing command iscompatible with a push protocol, wherein the web browser drawing updateis compatible with HTTP, wherein HTTP is a pull protocol (see, e.g.,item 1308-C in FIG. 13C); and

means for facilitating providing the web browser drawing update from thetranscoding server to the web browser of the client device, utilizingHTTP, as a response to at least one of the plurality of drawing requestsfrom the web browser (see, e.g., item 1310-C in FIG. 13C).

23. The apparatus of clause 22, wherein the means for handlingcomprises:

means for determining whether a drawing command is pending at thetranscoding server for the web browser;

means for storing the plurality of drawing requests in a drawingrequests queue as long poling requests if there is no pending drawingcommand; and

means for providing at least one of the plurality of drawing requests toan HTTP handler in the transcoding server, if there is a pending drawingcommand, to allow the HTTP handler to serve the pending drawing commandin response to the at least one of the plurality of drawing requests.

24. The apparatus of clause 22, wherein the remote desktop drawingcommand represents a portion of an entire image of a remote desktop ofthe remote machine,

wherein the means for translating comprises:

-   -   means for translating the remote desktop drawing command into a        Java graphics drawing command;    -   means for updating a portion of a Java bitmap of the entire        image of the remote desktop in response to the Java graphics        drawing command;    -   means for generating coordinates of the updated portion of the        Java bitmap based on the Java graphics drawing command;    -   means for generating an image file based on the updated portion        of the Java bitmap, wherein the image file is compatible with        the web browser; and    -   means for obtaining drawing coordinates for the image file based        on the coordinates of the updated portion of the Java bitmap,

wherein the web browser drawing update comprises the image file and thedrawing coordinates.

25. The apparatus of clause 22, wherein the means for handlingcomprises:

means for determining whether a drawing command is pending at thetranscoding server for the web browser;

means for storing the plurality of drawing requests in a drawingrequests queue as long poling requests if there is no pending drawingcommand; and

means for providing at least one of the plurality of drawing requests toan HTTP handler in the transcoding server, if there is a pending drawingcommand, to allow the HTTP handler to serve the pending drawing commandin response to the at least one of the plurality of drawing requests.

26. The apparatus of clause 22, wherein the means for facilitatingproviding comprises:

means for placing, at the HTTP handler, the drawing coordinates into anHTTP header of a single HTTP transmission response to the web browser;and

means for including, at the HTTP handler, the image file into the singleHTTP transmission response to the web browser to facilitate providingthe image file and the drawing coordinates together to the web browserin the single HTTP transmission response.

27. The apparatus of clause 22, further comprising:

means for sending a notification to the drawing requests queue, when adrawing commands queue has new coordinates, to allow at least one of theplurality of drawing requests in the drawing requests queue to beforwarded to the HTTP handler.

28. The apparatus of clause 22, further comprising:

means for receiving a new drawing request from the web browser, inresponse to facilitating providing the web browser drawing update fromthe transcoding server to the web browser of the client device as aresponse to the at least one of the plurality of drawing requests fromthe web browser.

29. The apparatus of clause 22, further comprising:

means for receiving a request from the web browser to connect to theremote machine; and

means for facilitating providing a JavaScript client code to the webbrowser in response to the request to connect to the remote machine,

wherein the means for receiving the plurality of drawing requestscomprises means for receiving the plurality of drawing requests from theJavaScript client code,

wherein the means for facilitating providing the web browser drawingupdate comprises means for facilitating providing the web browserdrawing update to the JavaScript client code.

30. The apparatus of clause 29, further comprising: means forfacilitating deleting the JavaScript client code from the web browserwhen the remote desktop session is terminated.

31. The apparatus of clause 22, further comprising:

means for receiving a user input request from the web browser foraccessing or controlling a remote desktop of the remote machine,

means for translating the user input request into an input commandcompatible with the push protocol;

means for facilitating providing the input command to the remote machineutilizing the push protocol,

wherein the means for receiving the remote desktop drawing commandcomprises means for receiving the remote desktop drawing command inresponse to the input command.

32. The apparatus of clause 22, wherein the apparatus comprises thetranscoding server.

33. The apparatus of clause 22, wherein the apparatus comprises aprocessing system and a memory.

Illustration of Method/Apparatus/Machine Readable Storage Medium forFacilitating a Remote Desktop Session Between a Web Browser at a ClientDevice and a Remote Desktop Server at a Remote Machine Through aTranscoding Server, Utilizing an Adapter at the Transcoding Server(Described as Clauses).

The subject technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the subjecttechnology are described as numbered clauses (1, 2, 3, etc.) forconvenience. These are provided as examples, and do not limit thesubject technology. It is noted that any of the dependent clauses may becombined in any combination, and placed into a respective independentclause, e.g., clauses 1, 10, and 20. Clause 1 below is presented, forexample, with reference to FIGS. 14A-14C. The other clauses can bepresented in a similar manner.

1. A method (see, e.g., item 1400-A in FIG. 14A) for facilitating aremote desktop session between a web browser at a client device (see,e.g., 310 in FIG. 3A) and a remote desktop server at a remote machine(see, e.g., 320) through a transcoding server (see, e.g., 330),utilizing an adapter (see, e.g., 600 in FIG. 6) at the transcodingserver, the method comprising:

receiving, at the adapter, an input request from the web browserutilizing a request-response protocol, wherein the request-responseprotocol is a pull protocol (see, e.g., item 1402-A in FIG. 14A);

translating, at the adapter, the input request into an input commandcompatible with a remote desktop display protocol to be utilized by aremote desktop client at the transcoding server for facilitatingcommunication with the remote desktop server at the remote machine,wherein the remote desktop display protocol is a push protocol (see,e.g., item 1404-A in FIG. 14A);

providing the input command to a remote desktop client at thetranscoding server, to facilitate providing the input command to theremote desktop server utilizing the remote desktop display protocol(see, e.g., item 1406-A in FIG. 14A);

receiving, at the adapter, a remote desktop drawing command from theremote desktop server in response to the input command, wherein theremote desktop drawing command is based on an image of a remote desktopof the remote machine (see, e.g., item 1408-A in FIG. 14A); and

translating, at the adapter, the remote desktop drawing command into agraphics drawing command compatible with the transcoding server to allowthe transcoding server to facilitate providing a web browser drawingupdate to the web browser, wherein the web browser drawing update iscompatible with the web browser (see, e.g., item 1410-A in FIG. 14A).

2. The method of clause 1, wherein the request-response protocolcomprises hypertext transfer protocol (HTTP), wherein the graphicsdrawing command is a Java graphics drawing command, wherein thetranscoding server is a Java transcoding server, wherein the web browseris HTML5 compatible.

3. The method of clause 1, wherein the receiving the input requestcomprises receiving the input request from the web browser via an HTTPhandler of a web application container at the transcoding server,

wherein the receiving the remote desktop drawing command comprisesreceiving the remote desktop drawing command via the remote desktopclient using the remote desktop display protocol.

4. The method of clause 1, wherein the remote desktop drawing commandcomprises remote desktop drawing command parameters and bitmap datareceived from the remote desktop server,

wherein the translating the remote desktop drawing command comprises oneor more of: calculating new drawing command parameters based on theremote desktop drawing command parameters; adjusting the remote desktopdrawing command parameters; and making adjustments to the bitmap data.

5. The method of clause 1, further comprising:

generating an image based on the graphics drawing command; and

generating coordinates for the image based on the graphics drawingcommand,

wherein the image represents a portion of an entire image of the remotedesktop.

6. The method of clause 1, further comprising:

executing the graphics drawing command to generate and draw an imageinto a drawing commands queue at the transcoding server that isaccessible by a web application container at the transcoding server forcommunicating with the web browser;

generating coordinates for the image based on the graphics drawingcommand;

storing the coordinates in the drawing commands queue; and

after generating the coordinates, transmitting a notification to the webapplication container that a drawing command is ready to be served tothe web browser,

wherein the graphics drawing command represents a portion of an entireimage of the remote desktop.

7. The method of clause 1, further comprising:

receiving, via an HTTP handler of the transcoding server, a connectionrequest from the web browser; and

facilitating establishing, controlling or terminating the remote desktopsession between the remote desktop client and the remote desktop serverin response to the connection request, wherein the facilitating of theestablishing, controlling or terminating comprises:

-   -   generating a session control command based on the connection        request, wherein the session control command is compatible with        the remote desktop display protocol; and    -   facilitating transmitting the session control command to the        remote desktop server via the remote desktop client using the        remote desktop display protocol.

8. The method of clause 7, wherein the session control command comprisesat least one of: a command for starting the remote desktop session, acommand for stopping the remote desktop session, a credential, asetting, a preference, and a command for passing at least one of acredential, a setting, and a preference.

9. The method of clause 1, further comprising:

extracting coordinates from the graphics drawing command; and

updating at least a portion of an off-screen bitmap based on thegraphics drawing command, wherein the at least a portion of theoff-screen bitmap is associated with the coordinates, wherein theoff-screen bitmap represents an entire image of the remote desktop.

10. A machine-readable storage medium (see, e.g., 810, 819 in FIG. 8)encoded with instructions executable by a processing system (see, e.g.,802) to perform a method for facilitating a remote desktop sessionbetween a web browser at a client device (see, e.g., 310 in FIG. 3A) anda remote desktop server at a remote machine (see, e.g., 320) through atranscoding server (see, e.g., 330), utilizing an adapter (see, e.g.,600 in FIG. 6) at the transcoding server, the instructions comprisingcode for:

receiving, at the adapter, an input request from the web browserutilizing a request-response protocol, wherein the request-responseprotocol is a pull protocol (see, e.g., item 1402-B in FIG. 14B);

translating, at the adapter, the input request into an input commandcompatible with a remote desktop display protocol to be utilized by aremote desktop client at the transcoding server for facilitatingcommunication with the remote desktop server at the remote machine,wherein the remote desktop display protocol is a push protocol (see,e.g., item 1404-B in FIG. 14B);

providing the input command to a remote desktop client at thetranscoding server, to facilitate providing the input command to theremote desktop server utilizing the remote desktop display protocol(see, e.g., item 1406-B in FIG. 14B);

receiving, at the adapter, a remote desktop drawing command from theremote desktop server in response to the input command, wherein theremote desktop drawing command is based on an image of a remote desktopof the remote machine (see, e.g., item 1408-B in FIG. 14B); and

translating, at the adapter, the remote desktop drawing command into agraphics drawing command compatible with the transcoding server to allowthe transcoding server to facilitate providing a web browser drawingupdate to the web browser, wherein the web browser drawing update iscompatible with the web browser (see, e.g., item 1410-B in FIG. 14B).

11. The machine-readable storage medium of clause 10, wherein therequest-response protocol comprises hypertext transfer protocol (HTTP),wherein the graphics drawing command is a Java graphics drawing command,wherein the transcoding server is a Java transcoding server, wherein theweb browser is HTML5 compatible.

12. The machine-readable storage medium of clause 10, wherein thereceiving the input request comprises receiving the input request fromthe web browser via an HTTP handler of an application container at thetranscoding server,

wherein the receiving the remote desktop drawing command comprisesreceiving the remote desktop drawing command via the remote desktopclient using the remote desktop display protocol.

13. The machine-readable storage medium of clause 10, wherein the remotedesktop drawing command comprises remote desktop drawing commandparameters and bitmap data received from the remote desktop server,

wherein the translating the remote desktop drawing command comprises oneor more of: calculating new drawing command parameters based on theremote desktop drawing command parameters; adjusting the remote desktopdrawing command parameters; and making adjustments to the bitmap data.

The machine-readable storage medium of clause 10, wherein theinstructions further comprise code for:

generating an image based on the graphics drawing command; and

generating coordinates for the image based on the graphics drawingcommand,

wherein the image represents a portion of an entire image of the remotedesktop.

15. The machine-readable storage medium of clause 10, wherein theinstructions further comprise code for:

executing the graphics drawing command to generate and draw an imageinto a drawing commands queue at the transcoding server that isaccessible by a web application container at the transcoding server forcommunicating with the web browser;

generating coordinates for the image based on the graphics drawingcommand;

storing the coordinates in the drawing commands queue; and

after generating the coordinates, transmitting a notification to the webapplication container that a drawing command is ready to be served tothe web browser,

wherein the graphics drawing command represents a portion of an entireimage of the remote desktop.

16. The machine-readable storage medium of clause 10, wherein theinstructions further comprise code for:

receiving, via an HTTP handler of the transcoding server, a connectionrequest from the web browser; and

facilitating establishing, controlling or terminating the remote desktopsession between the remote desktop client and the remote desktop serverin response to the connection request, wherein the facilitating of theestablishing, controlling or terminating comprises:

-   -   generating a session control command based on the connection        request, wherein the session control command is compatible with        the remote desktop display protocol; and    -   facilitating transmitting the session control command to the        remote desktop server via the remote desktop client using the        remote desktop display protocol.

17. The machine-readable storage medium of clause 16, wherein thesession control command comprises at least one of: a command forstarting the remote desktop session, a command for stopping the remotedesktop session, a credential, a setting, a preference, and a commandfor passing at least one of a credential, a setting, and a preference.

18. The machine-readable storage medium of clause 10, wherein theinstructions further comprise code for:

extracting coordinates from the graphics drawing command; and

updating at least a portion of an off-screen bitmap based on thegraphics drawing command, wherein the at least a portion of theoff-screen bitmap is associated with the coordinates, wherein theoff-screen bitmap represents an entire image of the remote desktop.

19. A computing machine comprising the machine-readable storage mediumof clause 10, wherein the computing machine is the transcoding server.

20. An apparatus (see, e.g., item 1400-C in FIG. 14C) for facilitating aremote desktop session between a web browser at a client device (see,e.g., 310 in FIG. 3A) and a remote desktop server at a remote machine(see, e.g., 320) through a transcoding server (see, e.g., 330),utilizing an adapter (see, e.g., 600 in FIG. 6) at the transcodingserver, the apparatus comprising:

means for receiving an input request from the web browser utilizing arequest-response protocol, wherein the request-response protocol is apull protocol (see, e.g., item 1402-C in FIG. 14C);

means for translating the input request into an input command compatiblewith a remote desktop display protocol to be utilized by a remotedesktop client at the transcoding server for facilitating communicationwith the remote desktop server at the remote machine, wherein the remotedesktop display protocol is a push protocol (see, e.g., item 1404-C inFIG. 14C);

means for providing the input command to a remote desktop client at thetranscoding server, to facilitate providing the input command to theremote desktop server utilizing the remote desktop display protocol(see, e.g., item 1406-C in FIG. 14C);

means for receiving a remote desktop drawing command from the remotedesktop server in response to the input command, wherein the remotedesktop drawing command is based on an image of a remote desktop of theremote machine (see, e.g., item 1408-C in FIG. 14C); and

means for translating the remote desktop drawing command into a graphicsdrawing command compatible with the transcoding server to allow thetranscoding server to facilitate providing a web browser drawing updateto the web browser, wherein the web browser drawing update is compatiblewith the web browser (see, e.g., item 1410-C in FIG. 14C).

21. The apparatus of clause 20, wherein the request-response protocolcomprises hypertext transfer protocol (HTTP), wherein the graphicsdrawing command is a Java graphics drawing command, wherein thetranscoding server is a Java transcoding server, wherein the web browseris HTML5 compatible.

22. The apparatus of clause 20, wherein the means for receiving theinput request comprises means for receiving the input request from theweb browser via an HTTP handler of a web application container at thetranscoding server,

wherein the means for receiving the remote desktop drawing commandcomprises means for receiving the remote desktop drawing command via theremote desktop client using the remote desktop display protocol.

23. The apparatus of clause 20, wherein the remote desktop drawingcommand comprises remote desktop drawing command parameters and bitmapdata received from the remote desktop server,

wherein the means for translating the remote desktop drawing commandcomprises one or more of: means for calculating new drawing commandparameters based on the remote desktop drawing command parameters; meansfor adjusting the remote desktop drawing command parameters; and meansfor making adjustments to the bitmap data.

24. The apparatus of clause 20, further comprising:

means for generating an image based on the graphics drawing command; and

means for generating coordinates for the image based on the graphicsdrawing command,

wherein the image represents a portion of an entire image of the remotedesktop.

25. The apparatus of clause 20, further comprising:

means for executing the graphics drawing command to generate and draw animage into a drawing commands queue at the transcoding server that isaccessible by a web application container at the transcoding server forcommunicating with the web browser;

means for generating coordinates for the image based on the graphicsdrawing command;

means for storing the coordinates in the drawing commands queue; and

means for transmitting, after generating the coordinates, a notificationto the web application container that a drawing command is ready to beserved to the web browser,

wherein the graphics drawing command represents a portion of an entireimage of the remote desktop.

26. The apparatus of clause 20, further comprising:

means for receiving, via an HTTP handler of the transcoding server, aconnection request from the web browser; and

means for facilitating establishing, controlling or terminating theremote desktop session between the remote desktop client and the remotedesktop server in response to the connection request, wherein the meansfor facilitating of the establishing, controlling or terminatingcomprises:

-   -   means for generating a session control command based on the        connection request, wherein the session control command is        compatible with the remote desktop display protocol; and    -   means for facilitating transmitting the session control command        to the remote desktop server via the remote desktop client using        the remote desktop display protocol.

27. The apparatus of clause 26, wherein the session control commandcomprises at least one of: a command for starting the remote desktopsession, a command for stopping the remote desktop session, acredential, a setting, a preference, and a command for passing at leastone of a credential, a setting, and a preference.

28. The apparatus of clause 20, further comprising:

means for extracting coordinates from the graphics drawing command; and

means for updating at least a portion of an off-screen bitmap based onthe graphics drawing command, wherein the at least a portion of theoff-screen bitmap is associated with the coordinates, wherein theoff-screen bitmap represents an entire image of the remote desktop.

29. The apparatus of clause 20, wherein the apparatus comprises thetranscoding server.

30. The apparatus of clause 20, wherein the apparatus comprises aprocessing system and a memory.

Illustration of Method/Apparatus/Machine Readable Storage Medium forFacilitating Accessing and Controlling a Remote Desktop of a RemoteMachine in Real Time from a Web Browser at a Client Device Via aHypertext Transfer Protocol (Http) Handler and a Remote Desktop ClientAdapter for a Transcoding Server (Described as Clauses).

The subject technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the subjecttechnology are described as numbered clauses (1, 2, 3, etc.) forconvenience. These are provided as examples, and do not limit thesubject technology. It is noted that any of the dependent clauses may becombined in any combination, and placed into a respective independentclause, e.g., clauses 1, 10, and 18. Clause 1 below is presented, forexample, with reference to FIGS. 15A-15E. The other clauses can bepresented in a similar manner.

1. A machine-readable storage medium (see, e.g., item 1500-A in FIG.15A) comprising code for facilitating accessing and controlling a remotedesktop of a remote machine (see, e.g., 320 in FIG. 3A) in real timefrom a web browser (see, e.g., 500 of FIG. 5) at a client device (see,e.g., 310 of FIG. 3A) via a hypertext transfer protocol (HTTP) handler(see, e.g., 422 of FIG. 4A) and a remote desktop client adapter (see,e.g., 430 of FIG. 4B) for a transcoding server (see, e.g., 330 of FIG.3A), the machine-readable storage medium comprising:

the HTTP handler (see, e.g., item 1502-A of FIG. 15A); and

the remote desktop client adapter (see, e.g., item 1504-A of FIG. 15A);

wherein the HTTP handler is configured to receive a connection requestand a user input request from the web browser utilizing HTTP, to providethe connection request and the user input request to the remote desktopclient adapter, and to facilitate providing a web browser drawing updateto the web browser in response to a drawing request from the webbrowser, wherein the web browser drawing update is compatible with theweb browser,

wherein the remote desktop client adapter is configured to receive theconnection request and the user input request, to translate theconnection request into a session control command compatible with aremote desktop display protocol, and to translate the user input requestinto a remote desktop input command compatible with the remote desktopdisplay protocol,

wherein the remote desktop client adapter is configured to facilitateproviding the session control command to a remote desktop client forproviding the session control command to a remote desktop server of theremote machine and for establishing, controlling or terminating a remotedesktop session with the remote desktop server,

wherein the remote desktop client adapter is configured to facilitateproviding the remote desktop input command to the remote desktop clientfor providing the remote desktop input command to the remote desktopserver,

wherein the remote desktop client adapter is configured to receive aremote desktop drawing command from the remote desktop server via theremote desktop client in response to the remote desktop input command,wherein the remote desktop drawing command is compatible with the remotedesktop display protocol,

wherein the remote desktop client adapter is configured to translate theremote desktop drawing command into a graphics drawing commandcompatible with the transcoding server, and to update a portion of animage representing the entire remote desktop and coordinates based onthe graphics drawing command, and

wherein the HTTP handler is configured to generate an image file basedon the updated portion of the image and to obtain drawing coordinatesbased on the coordinates in response to the drawing request, wherein theweb browser drawing update comprises the image file and the drawingcoordinates,

wherein the remote desktop drawing command represents a portion of theentire remote desktop,

wherein the remote desktop display protocol is a push protocol, and HTTPis a pull protocol.

2. The machine-readable storage medium of clause 1, wherein the userinput request comprises at least one of a mouse event, a keyboard event,and a touch event.

3. The machine-readable storage medium of clause 1, wherein the sessioncontrol command relates to establishing or controlling a connectionbetween the remote desktop client and the remote desktop server andcomprises at least one of: a command for starting the remote desktopsession, a command for stopping the remote desktop session, acredential, a setting, a preference, and a command for passing at leastone of a credential, a setting, and a preference.

4. The machine-readable storage medium of clause 1, wherein the graphicsdrawing command is a Java graphics drawing command, wherein thetranscoding server is a Java transcoding server, and wherein the webbrowser is HTML5 compatible.

5. The machine-readable storage medium of clause 1, wherein the remotedesktop client adapter is configured to place the image and thecoordinates into a drawing commands queue,

wherein the machine-readable storage medium further comprises a longpolling handler,

wherein the long polling handler is configured to receive the drawingrequest from the web browser utilizing HTTP, to forward the drawingrequest to the HTTP handler if coordinates for an image are pending inthe drawing commands queue, to place the drawing request into a drawingrequests queue if coordinates for an image are not pending in thedrawing commands, and

wherein the drawing commands queue is configured to send a notificationto the drawing requests queue if the drawing commands queue receives anew drawing command comprising an image and coordinates for an image.

6. The machine-readable storage medium of clause 1, further comprising adrawing requests queue configured to forward the drawing request to theHTTP handler in response to a notification from a drawing commands queuethat a drawing command is pending for the web browser.

7. The machine-readable storage medium of clause 1, wherein the HTTPhandler is configured to place the drawing coordinates into a section ofan HTTP header, wherein the HTTP handler is configured to facilitateproviding the image file and the drawing coordinates together to the webbrowser in a single HTTP transmission response for drawing a displayimage at the web browser, wherein the display image represents theupdated portion of the image representing the entire remote desktop.

8. The machine-readable storage medium of clause 1, wherein the HTTPhandler is configured to facilitate providing script client codecompatible with the web browser to the web browser if the connectionrequest from the web browser comprises a request to connect to theremote machine.

9. A computing machine comprising the machine-readable storage medium ofclause 1, wherein the computing machine is the transcoding server.

10. A method (see, e.g., item 1500-B of FIG. 15B and item 1500-C of FIG.15C) for facilitating accessing and controlling a remote desktop of aremote machine (see, e.g., 320 of FIG. 3A) in real time from a webbrowser (see, e.g., 500 of FIG. 5) at a client device (see, e.g., 310 ofFIG. 3A) utilizing a transcoding server (see, e.g., 330 of FIG. 3A), themethod comprising:

receiving, at the transcoding server, a connection request from the webbrowser utilizing HTTP (see, e.g., item 1502-B of FIG. 15B);

translating, at the transcoding server, the connection request into asession control command compatible with a remote desktop displayprotocol (see, e.g., item 1504-B of FIG. 15B);

providing the session control command to a remote desktop client of thetranscoding server for providing the session control command to a remotedesktop server of the remote machine and for establishing, controllingor terminating a remote desktop session with the remote desktop server(see, e.g., item 1506-B of FIG. 15B);

receiving, at the transcoding server, a user input request from the webbrowser utilizing HTTP (see, e.g., item 1508-B of FIG. 15B),

translating, at the transcoding server, the user input request into aremote desktop input command compatible with the remote desktop displayprotocol (see, e.g., item 1510-B of FIG. 15B);

providing the remote desktop input command to the remote desktop clientfor providing the remote desktop input command to the remote desktopserver (see, e.g., item 1512-B of FIG. 15B),

receiving, at the transcoding server, a remote desktop drawing commandfrom the remote desktop server via the remote desktop client in responseto the remote desktop input command, wherein the remote desktop drawingcommand is compatible with the remote desktop display protocol, andwherein the remote desktop drawing command represents a portion of anentire image of the remote desktop (see, e.g., item 1502-C of FIG. 15C);

translating, at the transcoding server, the remote desktop drawingcommand into a graphics drawing command compatible with the transcodingserver (see, e.g., item 1504-C of FIG. 15C);

updating, at the transcoding server, a portion of an image andcoordinates based on the graphics drawing command (see, e.g., item1506-C of FIG. 15C);

generating, at the transcoding server, an image file based on theupdated portion of the image (see, e.g., item 1508-C of FIG. 15C);

obtaining drawing coordinates based on the coordinates (see, e.g., item1510-C of FIG. 15C); and

facilitating providing a web browser drawing update to the web browserin response to a drawing request from the web browser, wherein the webbrowser drawing update comprises the image file and the drawingcoordinates, and wherein the web browser drawing update is compatiblewith the web browser (see, e.g., item 1512-C of FIG. 15C),

wherein the remote desktop drawing command represents a portion of theentire remote desktop, and the image represents the entire remotedesktop,

wherein the remote desktop display protocol is a push protocol, and HTTPis a pull protocol.

11. The method of clause 10, wherein the user input request comprises atleast one of a mouse event, a keyboard event, and a touch event.

12. The method of clause 10, wherein the session control commandcomprises at least one of: a command for starting the remote desktopsession, a command for stopping the remote desktop session, acredential, a setting, a preference, and a command for passing at leastone of a credential, a setting, and a preference.

13. The method of clause 10, wherein the graphics drawing command is aJava graphics drawing command, wherein the transcoding server is a Javatranscoding server, and wherein the web browser is HTML5 compatible.

14. The method of clause 10, wherein the updating a portion of an imageand coordinates comprises storing the portion of the image and thecoordinates into a drawing commands queue,

wherein the method further comprises: receiving the drawing request fromthe web browser utilizing HTTP; forwarding the drawing request to anHTTP handler if coordinates for an image are pending in the drawingcommands queue; placing the drawing request into a drawing requestsqueue if coordinates for an image are not pending in the drawingcommands, and

wherein the method further comprises: sending a notification to thedrawing requests queue if the drawing commands queue receives a newdrawing command comprising an image and coordinates for an image.

15. The method of clause 10, further comprising forwarding the drawingrequest to an HTTP handler in response to a notification from a drawingcommands queue that a drawing command is pending for the web browser.

16. The method of clause 10, further comprising placing the drawingcoordinates into a section of an HTTP header, wherein the facilitatingproviding the web browser drawing update comprises facilitatingproviding the image file and the drawing coordinates together to the webbrowser in a single HTTP transmission response for drawing a displayimage at the web browser, wherein the display image represents theupdated portion of the image representing the entire remote desktop.

17. The method of clause 10, further comprising facilitate providingscript client code compatible with the web browser, to the web browser,if the connection request from the web browser comprises a request toconnect to the remote machine.

18. A transcoding server (see, e.g., item 1500-D of FIG. 15D and item1500-E of FIG. 15E) for facilitating accessing and controlling a remotedesktop of a remote machine (see, e.g., 320 of FIG. 3A) in real timefrom a web browser (see, e.g., 500 of FIG. 5) at a client device (see,e.g., 310 of FIG. 3A), the transcoding server comprising:

means for receiving a connection request from the web browser utilizingHTTP (see, e.g., item 1502-D in FIG. 15D);

means for translating the connection request into a session controlcommand compatible with a remote desktop display protocol (see, e.g.,item 1504-D in FIG. 15D);

means for providing the session control command to a remote desktopclient of the transcoding server for providing the session controlcommand to a remote desktop server of the remote machine and forestablishing, controlling or terminating a remote desktop session withthe remote desktop server (see, e.g., item 1506-D in FIG. 15D);

means for receiving a user input request from the web browser utilizingHTTP (see, e.g., item 1508-D in FIG. 15D),

means for translating the user input request into a remote desktop inputcommand compatible with the remote desktop display protocol (see, e.g.,item 1510-D in FIG. 15D);

means for providing the remote desktop input command to the remotedesktop client for providing the remote desktop input command to theremote desktop server (see, e.g., item 1512-D in FIG. 15D),

means for receiving a remote desktop drawing command from the remotedesktop server via the remote desktop client in response to the remotedesktop input command, wherein the remote desktop drawing command iscompatible with the remote desktop display protocol, and wherein theremote desktop drawing command represents a portion of an entire imageof the remote desktop (see, e.g., item 1502-E in FIG. 15E);

means for translating the remote desktop drawing command into a graphicsdrawing command compatible with the transcoding server (see, e.g., item1504-E in FIG. 15E);

means for updating a portion of an image and coordinates based on thegraphics drawing command (see, e.g., item 1506-E in FIG. 15E);

means for generating an image file based on the updated portion of theimage (see, e.g., item 1508-E in FIG. 15E);

means for obtaining drawing coordinates based on the coordinates (see,e.g., item 1510-E in FIG. 15E); and

means for facilitating providing a web browser drawing update to the webbrowser in response to a drawing request from the web browser, whereinthe web browser drawing update comprises the image file and the drawingcoordinates, and wherein the web browser drawing update is compatiblewith the web browser (see, e.g., item 1512-E in FIG. 15E),

wherein the remote desktop drawing command represents a portion of theentire remote desktop, and the image represents the entire remotedesktop,

wherein the remote desktop display protocol is a push protocol, and HTTPis a pull protocol.

19. The transcoding server of clause 18, wherein the user input requestcomprises at least one of a mouse event, a keyboard event, and a touchevent.

20. The transcoding server of clause 18, wherein the session controlcommand comprises at least one of: a command for starting the remotedesktop session, a command for stopping the remote desktop session, acredential, a setting, a preference, and a command for passing at leastone of a credential, a setting, and a preference.

21. The transcoding server of clause 18, wherein the graphics drawingcommand is a Java graphics drawing command, wherein the transcodingserver is a Java transcoding server, and wherein the web browser isHTML5 compatible.

22. The transcoding server of clause 18, wherein the means for updatinga portion of an image and coordinates comprises means for storing theportion of the image and the coordinates into a drawing commands queue,

wherein the transcoding server further comprises: means for receivingthe drawing request from the web browser utilizing HTTP; means forforwarding the drawing request to an HTTP handler if coordinates for animage are pending in the drawing commands queue; means for placing thedrawing request into a drawing requests queue if coordinates for animage are not pending in the drawing commands, and

wherein the transcoding server further comprises: means for sending anotification to the drawing requests queue if the drawing commands queuereceives a new drawing command comprising an image and coordinates foran image.

23. The transcoding server of clause 18, further comprising means forforwarding the drawing request to an HTTP handler in response to anotification from a drawing commands queue that a drawing command ispending for the web browser.

24. The transcoding server of clause 18, further comprising means forplacing the drawing coordinates into a section of an HTTP header,wherein the means for facilitating providing the web browser drawingupdate comprises means for facilitating providing the image file and thedrawing coordinates together to the web browser in a single HTTPtransmission response for drawing a display image at the web browser,wherein the display image represents the updated portion of the imagerepresenting the entire remote desktop.

25. The transcoding server of clause 18, further comprising means forfacilitate providing script client code compatible with the web browser,to the web browser, if the connection request from the web browsercomprises a request to connect to the remote machine.

26. A processor comprising modules configured to perform the method ofany one of the foregoing clauses in paragraphs [0132]-[0143].

27. A machine-readable storage medium comprising code for causing thetranscoding server to perform the method of any one of the foregoingclauses in paragraphs [0132]-[0143].

28. The machine-readable storage medium of clause 27, wherein thetranscoding server comprises the machine-readable storage medium.

29. An apparatus comprising means for performing the method of any oneof the foregoing clauses in paragraphs [0132]-[0143].

30. The apparatus of clause 29, wherein the apparatus comprises atranscoding server.

31. The apparatus of clause 29, wherein the apparatus comprises aprocessing system and a memory.

33. An apparatus comprising components operable to perform the method ofany one of the foregoing clauses in paragraphs [0132]-[0143].

34. The apparatus of clause 33, wherein the apparatus comprises atranscoding server.

35. The apparatus of clause 33, wherein the apparatus comprises aprocessing system and a memory.

Those of skill in the art would appreciate that the various illustrativeblocks, modules, elements, components, methods, and algorithms describedherein may be implemented as electronic hardware, computer software, orcombinations of both.

For example, a module (e.g., an web application container, a longpolling handler module, a long polling handler, a drawing requestsqueue, an HTTP handler, an image conversion module, a drawing commandsqueue, a remote desktop client adapter, a remote desktop client, aremote desktop server, or other modules or functions) may be implementedas electronic hardware, computer software, or combinations of both.Modules may be considered in some aspects as “means for” accomplishingone or more functions or steps. In one aspect, a module(s) may be anapparatus since a module(s) may include instructions encoded or storedon a machine-readable medium, on another device, or on a portionthereof. In one aspect, a module(s) may be software (e.g., anapplication, a subroutine) stored in a machine-readable medium andexecutable by a processing system or a processor. In another aspect, amodule(s) may be hardware (e.g., machine-readable medium encoded withinstructions, a pre-programmed general-purpose computer with for exampleASIC or FPGA, or a special purpose electronic or optical device).

To illustrate this interchangeability of hardware and software, variousillustrative blocks, modules, elements, components, methods, andalgorithms have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application.

In one aspect of the disclosure, when actions or functions are describedas being performed by a module or a component (e.g., establishing,sending, receiving, providing, building, displaying, notifying,accepting, selecting, controlling, issuing, transmitting, reporting,pushing, or any other action or function), it is understood that suchactions or functions are performed by the module or the componentdirectly or indirectly. As an example, when a module is described asperforming an action, it is understood that the module may perform theaction directly or may perform the action indirectly, for example, byfacilitating such an action. For instance, when a session is describedas being established by a module, it is understood that the module mayestablish the session indirectly by facilitating an establishment of thesession. As yet another example, when an image is described as beingdisplayed or rendered by a module, it is understood that the image maybe displayed or rendered by the module either directly or indirectly.

Various components and blocks may be arranged differently (e.g.,arranged in a different order, or partitioned in a different way) allwithout departing from the scope of the subject technology. In oneaspect of the disclosure, the modules (or elements) recited in theaccompanying claims may be performed by one module or by a smallernumber of modules, and this arrangement is within the scope of theclaims. In another aspect, the modules (or elements) recited in theaccompanying claims may be performed by a larger number of modules, andthis arrangement is within the scope of the claims. In yet anotheraspect, a module (or an element) recited in the accompanying claims maybe performed by multiple modules, and this arrangement is within thescope of the claims.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed is an illustration of exemplary approaches. Basedupon design preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged. Some of the stepsmay be performed simultaneously. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. The previousdescription provides various examples of the subject technology, and thesubject technology is not limited to these examples. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element (e.g., acommand, a call, a handler, a device, a machine, etc.) in the singularis not intended to mean “one and only one” unless specifically sostated, but rather “one or more.” Unless specifically stated otherwise,the term “some” refers to one or more. Pronouns in the masculine (e.g.,his) include the feminine and neuter gender (e.g., her and its) and viceversa. Headings and subheadings, if any, are used for convenience onlyand do not limit the invention.

A phrase such as an “aspect” does not imply that such aspect isessential to the subject technology or that such aspect applies to allconfigurations of the subject technology. A disclosure relating to anaspect may apply to all configurations, or one or more configurations.An aspect may provide one or more examples of the disclosure. A phrasesuch as an aspect may refer to one or more aspects and vice versa. Aphrase such as an “embodiment” does not imply that such embodiment isessential to the subject technology or that such embodiment applies toall configurations of the subject technology. A disclosure relating toan embodiment may apply to all embodiments, or one or more embodiments.An embodiment may provide one or more examples of the disclosure. Aphrase such an embodiment may refer to one or more embodiments and viceversa. A phrase such as a “configuration” does not imply that suchconfiguration is essential to the subject technology or that suchconfiguration applies to all configurations of the subject technology. Adisclosure relating to a configuration may apply to all configurations,or one or more configurations. A configuration may provide one or moreexamples of the disclosure. A phrase such a configuration may refer toone or more configurations and vice versa.

The word “exemplary” is used herein to mean “serving as an example orillustration.” Any aspect or design described herein as “exemplary” isnot necessarily to be construed as preferred or advantageous over otheraspects or designs.

In one aspect, the term “compatible” may be used in a sense that a firstelement (e.g., a drawing command, an input call, an input command, aconnection request, a drawing request, etc.) is compatible with a secondelement (e.g., a remote desktop display protocol, a remote desktopclient, a remote desktop server, a transcoding server, a web browser, aclient device, a remote machine, HTML5, HTTP, etc.) so that the firstelement can be recognized or understood by the second element, can beprocessed by the second element, or can be utilized by or with thesecond element.

All structural and functional equivalents to the elements of the variousaspects described throughout this disclosure that are known or latercome to be known to those of ordinary skill in the art are expresslyincorporated herein by reference and are intended to be encompassed bythe claims. Moreover, nothing disclosed herein is intended to bededicated to the public regardless of whether such disclosure isexplicitly recited in the claims. No claim element is to be construedunder the provisions of 35 U.S.C. §112, sixth paragraph, unless theelement is expressly recited using the phrase “means for” or, in thecase of a method claim, the element is recited using the phrase “stepfor.” Furthermore, to the extent that the term “include,” “have,” or thelike is used in the description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprise” as “comprise” isinterpreted when employed as a transitional word in a claim.

What is claimed is:
 1. A non-transitory machine-readable storage mediumcomprising code for facilitating accessing and controlling a remotedesktop of a remote machine, the machine-readable storage mediumcomprising: a hypertext transfer protocol (HTTP) handler of atranscoding server; and a remote desktop client adapter of thetranscoding server, wherein the HTTP handler is configured to: receive aconnection request and a user input request from a web browser utilizingHTTP, provide the connection request and the user input request to theremote desktop client adapter, and provide a web browser drawing updateto the web browser in response to a drawing request from the webbrowser, wherein the web browser drawing update is compatible with theweb browser, wherein the remote desktop client adapter is configured to:receive the connection request and the user input request, translate theconnection request into a session control command compatible with aremote desktop display protocol, translate the user input request into aremote desktop input command compatible with the remote desktop displayprotocol, provide the session control command to a remote desktop clientfor providing the session control command to a remote desktop server ofthe remote machine and for establishing, controlling or terminating aremote desktop session with the remote desktop server, provide theremote desktop input command to the remote desktop client for providingthe remote desktop input command to the remote desktop server, receive aremote desktop drawing command from the remote desktop server via theremote desktop client in response to the remote desktop input command,wherein the remote desktop drawing command is compatible with the remotedesktop display protocol and represents a portion of the entire remotedesktop, translate the remote desktop drawing command into a graphicsdrawing command compatible with the transcoding server, and update aportion of an image representing the entire remote desktop andcoordinates based on the graphics drawing command, and wherein the HTTPhandler is configured to: generate an image file based on the updatedportion of the image, obtain drawing coordinates based on thecoordinates in response to the drawing request, wherein the web browserdrawing update comprises the image file and the drawing coordinates, andprovide the web browser drawing update to the web browser in real timeincluding placing the drawing coordinates into a cookie to be providedto the web browser.
 2. The non-transitory machine-readable storagemedium of claim 1, wherein the user input request comprises at least oneof a mouse event, a keyboard event, and a touch event.
 3. Thenon-transitory machine-readable storage medium of claim 1, wherein thesession control command relates to establishing or controlling aconnection between the remote desktop client and the remote desktopserver and comprises at least one of: a command for starting the remotedesktop session, a command for stopping the remote desktop session, acredential, a setting, a preference, and a command for passing at leastone of a credential, a setting, and a preference.
 4. The non-transitorymachine-readable storage medium of claim 1, wherein the graphics drawingcommand is a Java graphics drawing command, wherein the transcodingserver is a Java transcoding server.
 5. The non-transitorymachine-readable storage medium of claim 1, wherein the remote desktopclient adapter is configured to place the image and the coordinates intoa drawing commands queue, wherein the machine-readable storage mediumfurther comprises a long polling handler, wherein the long pollinghandler is configured to receive the drawing request from the webbrowser utilizing HTTP, to forward the drawing request to the HTTPhandler if coordinates for an image are pending in the drawing commandsqueue, to place the drawing request into a drawing requests queue ifcoordinates for an image are not pending in the drawing commands, andwherein the drawing commands queue is configured to send a notificationto the drawing requests queue if the drawing commands queue receives anew drawing command comprising an image and coordinates for an image. 6.The non-transitory machine-readable storage medium of claim 1, furthercomprising a drawing requests queue configured to forward the drawingrequest to the HTTP handler in response to a notification from a drawingcommands queue that a drawing command is pending for the web browser. 7.The non-transitory machine-readable storage medium of claim 1, whereinthe HTTP handler is configured to place the drawing coordinates into asection of an HTTP header, wherein the HTTP handler is configured tofacilitate providing the image file and the drawing coordinates togetherto the web browser in a single HTTP transmission response for drawing adisplay image at the web browser, wherein the display image representsthe updated portion of the image representing the entire remote desktop.8. The non-transitory machine-readable storage medium of claim 1,wherein the HTTP handler is configured to provide script client codecompatible with the web browser to the web browser if the connectionrequest from the web browser comprises a request to connect to theremote machine.
 9. A method for facilitating accessing and controlling aremote desktop of a remote machine, the method comprising: receiving, ata transcoding server, a connection request from a web browser utilizinghypertext transfer protocol (HTTP), translating, at the transcodingserver, the connection request into a session control command compatiblewith a remote desktop display protocol; providing the session controlcommand to a remote desktop client of the transcoding server forproviding the session control command to a remote desktop server of theremote machine and for establishing, controlling or terminating a remotedesktop session with the remote desktop server; receiving, at thetranscoding server, a user input request from the web browser utilizingHTTP, translating, at the transcoding server, the user input requestinto a remote desktop input command compatible with the remote desktopdisplay protocol; providing the remote desktop input command to theremote desktop client for providing the remote desktop input command tothe remote desktop server; receiving, at the transcoding server, aremote desktop drawing command from the remote desktop server via theremote desktop client in response to the remote desktop input command,wherein the remote desktop drawing command is compatible with the remotedesktop display protocol, and wherein the remote desktop drawing commandrepresents a portion of an entire image of the remote desktop;translating, at the transcoding server, the remote desktop drawingcommand into a graphics drawing command compatible with the transcodingserver; updating, at the transcoding server, a portion of an image andcoordinates based on the graphics drawing command; generating, at thetranscoding server, an image file based on the updated portion of theimage; obtaining drawing coordinates based on the coordinates; andproviding a web browser drawing update to the web browser in real timein response to a drawing request from the web browser including placingthe drawing coordinates into a cookie to be provided to the web browser,wherein the web browser drawing update comprises the image file and thedrawing coordinates, and wherein the web browser drawing update iscompatible with the web browser.
 10. The method of claim 9, wherein theuser input request comprises at least one of a mouse event, a keyboardevent, and a touch event.
 11. The method of claim 9, wherein the sessioncontrol command comprises at least one of: a command for starting theremote desktop session, a command for stopping the remote desktopsession, a credential, a setting, a preference, and a command forpassing at least one of a credential, a setting, and a preference. 12.The method of claim 9, wherein the graphics drawing command is a Javagraphics drawing command, wherein the transcoding server is a Javatranscoding server.
 13. The method of claim 9, wherein the updating aportion of an image and coordinates comprises storing the portion of theimage and the coordinates into a drawing commands queue, wherein themethod further comprises: receiving the drawing request from the webbrowser utilizing HTTP; forwarding the drawing request to an HTTPhandler if coordinates for an image are pending in the drawing commandsqueue; placing the drawing request into a drawing requests queue ifcoordinates for an image are not pending in the drawing commands, andsending a notification to the drawing requests queue if the drawingcommands queue receives a new drawing command comprising an image andcoordinates for an image.
 14. The method of claim 9, further comprisingforwarding the drawing request to an HTTP handler in response to anotification from a drawing commands queue that a drawing command ispending for the web browser.
 15. The method of claim 9, furthercomprising placing the drawing coordinates into a section of an HTTPheader, wherein the providing the web browser drawing update comprisesproviding the image file and the drawing coordinates together to the webbrowser in a single HTTP transmission response for drawing a displayimage at the web browser, wherein the display image represents theupdated portion of the image representing the entire remote desktop. 16.The method of claim 9, further comprising providing script client codecompatible with the web browser, to the web browser, if the connectionrequest from the web browser comprises a request to connect to theremote machine.